CVE-2026-53089

bpf: Fix use-after-free in offloaded map/prog info fill

HIGH
7.8
CVSS Score
Published: June 24, 2026 at 04:30 PM UTC
Updated: September 2, 2026 at 02:02 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.16 ≤ v < 5.10.2694.16 ≤ v < 5.15.2204.16 ≤ v < 6.1.1874.16 ≤ v < 6.12.1084.16 ≤ v < 6.18.494.16 ≤ v < 6.6.1564.16 ≤ v < 7.0.104.16 ≤ v < 7.14.16675fc275a3a2d905535207237402c6d8dcb5fa4b
Vendor states this is fixed in 1a2dc103e16448d022a77ad5fc3234641436c4b7 (fixed)
Vendor states this is fixed in 43d6848a2a6c92ccfd614d9f0bb6fd85b95dfa9d (fixed)
Vendor states this is fixed in 5662dac41a3442aa378d7c405164903eb109fc05 (fixed)
Vendor states this is fixed in 642943ae5bdacabc8109dc4a5e0ebb4a6b99ef3e (fixed)
Vendor states this is fixed in 85dc711f742b192eb97c0e00b521312f5a7a415e (fixed)
Vendor states this is fixed in a0c584fc18056709c8e047a82a6045d6c209f4ce (fixed)
Vendor states this is fixed in a51e7fbe94a87e236631a83973d4f558310b2cd2 (fixed)
Vendor states this is fixed in fea55b034328feaafef75aee252f305e6f85a991 (fixed)
Vendor states this is fixed in 4.16 (unaffected)
Vendor states this is fixed in 5.10.269 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card