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

> A use-after-free vulnerability in the Linux kernel's BPF subsystem allows attackers to potentially execute code or escalate privileges during network namespace teardown.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 2 Sep 2026
- **Also known as:** AZL-90300, BELL-CVE-2026-53089, DEBIAN-CVE-2026-53089, GHSA-fwh4-95hv-8xhf, ROOT-OS-DEBIAN-11-CVE-2026-53089, ROOT-OS-DEBIAN-12-CVE-2026-53089, ROOT-OS-DEBIAN-13-CVE-2026-53089, ROOT-OS-UBUNTU-2204-CVE-2026-53089, ROOT-OS-UBUNTU-2404-CVE-2026-53089, UBUNTU-CVE-2026-53089

## What is CVE-2026-53089?

CVE-2026-53089 is a high-severity use after free vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-53089?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53089?

Apply the vendor's patch.

## Is CVE-2026-53089 being exploited?

There is no known exploitation of CVE-2026-53089 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53089 and fix it if it is affected.

What it is: CVE-2026-53089 is a high-severity use after free vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53089 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53089/ (Markdown: https://insights.sbomify.com/CVE-2026-53089/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53089
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53089
- OSV: https://osv.dev/vulnerability/CVE-2026-53089

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53089/
Summaries are generated and may contain mistakes; the official description above is the record.