VulnerabilityPublished 24 Jun 2026Updated 6 Nov 2026

CVE-2026-53089: Linux kernel · bpf: Fix use-after-free in offloaded map/prog info fill

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in fea55b034328feaafef75aee252f305e6f85a991 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in fea55b034328feaafef75aee252f305e6f85a991, a51e7fbe94a87e236631a83973d4f558310b2cd2, a0c584fc18056709c8e047a82a6045d6c209f4ce +5

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < fea55b034328feaafef75aee252f305e6f85a991	Fixed in fea55b034328feaafef75aee252f305e6f85a991
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < a51e7fbe94a87e236631a83973d4f558310b2cd2	Fixed in a51e7fbe94a87e236631a83973d4f558310b2cd2
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < a0c584fc18056709c8e047a82a6045d6c209f4ce	Fixed in a0c584fc18056709c8e047a82a6045d6c209f4ce
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < 642943ae5bdacabc8109dc4a5e0ebb4a6b99ef3e	Fixed in 642943ae5bdacabc8109dc4a5e0ebb4a6b99ef3e
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < 5662dac41a3442aa378d7c405164903eb109fc05	Fixed in 5662dac41a3442aa378d7c405164903eb109fc05
LinuxLinux	Affected ≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b, < 85dc711f742b192eb97c0e00b521312f5a7a415e	Fixed in 85dc711f742b192eb97c0e00b521312f5a7a415e

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free in offloaded map/prog info fill When querying info for an offloaded BPF map or program, bpf_map_offload_info_fill_ns() and bpf_prog_offload_info_fill_ns() obtain the network namespace with get_net(dev_net(offmap->netdev)). However, the associated netdev's netns may be racing with teardown during netns destruction. If the netns refcount has already reached 0, get_net() performs a refcount_t increment on 0, triggering: refcount_t: addition on 0; use-after-free. Although rtnl_lock and bpf_devs_lock ensure the netdev pointer remains valid, they cannot prevent the netns refcount from reaching zero. Fix this by using maybe_get_net() instead of get_net(). maybe_get_net() uses refcount_inc_not_zero() and returns NULL if the refcount is already zero, which causes ns_get_path_cb() to fail and the caller to return -ENOENT -- the correct behavior when the netns is being destroyed.

References

Community reviews

Loading reviews…