CVE-2026-98039bpf: Require MEM_PERCPU for percpu kptr stores
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Require MEM_PERCPU for percpu kptr stores map_kptr_match_type() treats perm_flags as the set of register type flags that a kptr field permits. Adding MEM_PERCPU to that set for BPF_KPTR_PERCPU does not require the source register to carry it, however. The subset test consequently accepts both a plain bpf_obj_new() allocation and a referenced kernel pointer into a __percpu_kptr map field. Loads from the field are always marked MEM_PERCPU. Consumers then treat the stored value as the cookie returned by bpf_percpu_obj_new(): per-CPU pointer helpers relocate it, and map teardown selects the per-CPU free path. A plain allocation can therefore provide an arbitrary kernel read/write, while a kernel pointer can be relocated into an invalid address or sent through a missing destructor. Require the source MEM_PERCPU flag to match the destination field kind. This preserves valid bpf_percpu_obj_new() stores and rejects both the program-BTF and kernel-BTF variants.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d – < aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f
- affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d – < 0bdd6121c8dd5f1764efe701ce26bb8e15acb172
- affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d – < ad4ebae5dbc2d47b544aa54f03c12490065be08a
- affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d – < 048029ba1c793f8cabc4ad5eea765da01903f8f1
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f (opens in a new tab)
- https://git.kernel.org/stable/c/0bdd6121c8dd5f1764efe701ce26bb8e15acb172 (opens in a new tab)
- https://git.kernel.org/stable/c/ad4ebae5dbc2d47b544aa54f03c12490065be08a (opens in a new tab)
- https://git.kernel.org/stable/c/048029ba1c793f8cabc4ad5eea765da01903f8f1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86692 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98039)Record last updated .