# CVE-2026-72402: bpf: Mask pseudo pointer values in verifier logs

> A local attacker can leak kernel pointer addresses via BPF verifier logs, bypassing KASLR protections.

- **Severity:** Not scored
- **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:** 15 Aug 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-96581, BELL-CVE-2026-72402, DEBIAN-CVE-2026-72402, GHSA-759v-33rj-5hjh, UBUNTU-CVE-2026-72402

## What is CVE-2026-72402?

CVE-2026-72402 is a vulnerability in Linux, published on 15 Aug 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: Mask pseudo pointer values in verifier logs

print_bpf_insn() masks ldimm64 immediates for pointer-bearing pseudo
sources when pointer leaks are not allowed, but the mask only covers
BPF_PSEUDO_MAP_FD and BPF_PSEUDO_MAP_VALUE.

BPF_PSEUDO_MAP_IDX, BPF_PSEUDO_MAP_IDX_VALUE, and BPF_PSEUDO_BTF_ID can
also be resolved to kernel pointer values before the verifier log prints
the instruction. Include them in the existing pointer classification so
the log prints 0x0 instead of the rewritten address.

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


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

Apply the vendor's patch.

## Is CVE-2026-72402 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72402 is a vulnerability in Linux, published on 15 Aug 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-72402 in the wild and no public exploit code.

Affected product: Linux. 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-72402/ (Markdown: https://insights.sbomify.com/CVE-2026-72402/index.md)
```

## Sources

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

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