bpf: Require MEM_PERCPU for percpu kptr stores
Summary
| CVE | CVE-2026-98039 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:32 UTC |
| Updated | 2026-09-25 11:17:32 UTC |
| 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.053850000 (date 2026-09-27)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f git | Not specified |
| CNA | Linux | Linux | affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d 0bdd6121c8dd5f1764efe701ce26bb8e15acb172 git | Not specified |
| CNA | Linux | Linux | affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d ad4ebae5dbc2d47b544aa54f03c12490065be08a git | Not specified |
| CNA | Linux | Linux | affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d 048029ba1c793f8cabc4ad5eea765da01903f8f1 git | Not specified |
| CNA | Linux | Linux | affected 6.7 | Not specified |
| CNA | Linux | Linux | unaffected 6.7 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/048029ba1c793f8cabc4ad5eea765da01903f8f1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0bdd6121c8dd5f1764efe701ce26bb8e15acb172 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ad4ebae5dbc2d47b544aa54f03c12490065be08a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.