bpf: Require MEM_PERCPU for percpu kptr stores
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ad4ebae5dbc2d47b544aa54f03c12490065be08a, Kernel 048029ba1c793f8cabc4ad5eea765da01903f8f1, Kernel 0bdd6121c8dd5f1764efe701ce26bb8e15acb172 and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=36d8bdf75a93190e5669b9d1d95994e13e15ba1d <ad4ebae5dbc2d47b544aa54f03c12490065be08a, >=36d8bdf75a93190e5669b9d1d95994e13e15ba1d <048029ba1c793f8cabc4ad5eea765da01903f8f1, >=36d8bdf75a93190e5669b9d1d95994e13e15ba1d <0bdd6121c8dd5f1764efe701ce26bb8e15acb172, >=36d8bdf75a93190e5669b9d1d95994e13e15ba1d <aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f, =6.7 | ad4ebae5dbc2d47b544aa54f03c12490065be08a, 048029ba1c793f8cabc4ad5eea765da01903f8f1, 0bdd6121c8dd5f1764efe701ce26bb8e15acb172, aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f |
| linux-kernel: Kernel | >=6.19.0 <7.2.7, >=6.7.0 <6.12.111, >=6.13.0 <6.18.53 | 7.2.7, 6.12.111, 6.18.53 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket