CVE-2026-72402: bpf: Mask pseudo pointer values in verifier logs
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1c53d16b174dd9e02243fc0e85089e2aa6a0d21a, 6181239115e19cda4b483a2604193a9379cbd28f, 72a85e9464a5332fb2cd7efd26d9295275ceda2d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 1c53d16b174dd9e02243fc0e85089e2aa6a0d21a, 6181239115e19cda4b483a2604193a9379cbd28f, 72a85e9464a5332fb2cd7efd26d9295275ceda2d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before b767a5d7c6cb595f9feb00b5af96191a59efca26affected · git
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before 6181239115e19cda4b483a2604193a9379cbd28faffected · git
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before c727b3d50ecb0f4992a964360771040a84026914affected · git
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before b96cb1235fcaa687291b1e1d910f0930d1939919affected · git
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before 1c53d16b174dd9e02243fc0e85089e2aa6a0d21aaffected · git
- 4976b718c3551faba2c0616ef55ebeb74db1c5ca and later · before 72a85e9464a5332fb2cd7efd26d9295275ceda2daffected · git
- before 5.10not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72398Aug 15, 2026 · sctp: add INIT verification after cookie unpacking39Monitor
- ← EarlierCVE-2026-72400Aug 15, 2026 · seg6: validate SRH length before reading fixed fields31Monitor
- Later →CVE-2026-72404Aug 15, 2026 · tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c53d16b174dd9e02243fc0e85089e2aa6a0d21a | Vendor (CNA) |
| Linux Linux | 6181239115e19cda4b483a2604193a9379cbd28f | Vendor (CNA) |
| Linux Linux | 72a85e9464a5332fb2cd7efd26d9295275ceda2d | Vendor (CNA) |
| Linux Linux | b767a5d7c6cb595f9feb00b5af96191a59efca26 | Vendor (CNA) |
| Linux Linux | b96cb1235fcaa687291b1e1d910f0930d1939919 | Vendor (CNA) |
| Linux Linux | c727b3d50ecb0f4992a964360771040a84026914 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6181239115e19cda4b483a2604193a9379cbd28f
- git.kernel.org/stable/c/72a85e9464a5332fb2cd7efd26d9295275ceda2d
- git.kernel.org/stable/c/b767a5d7c6cb595f9feb00b5af96191a59efca26
- git.kernel.org/stable/c/b96cb1235fcaa687291b1e1d910f0930d1939919
- git.kernel.org/stable/c/c727b3d50ecb0f4992a964360771040a84026914
Vendor advisories and official records. Exploit/PoC links are deliberately left out.