bpf: Require a BPF cpumask for bpf_cpumask_populate()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0cfc9348a045da64955af2dd6902e66dfc7d6469, Kernel 8740156ad33be5071b588b594c55f279457f667c and Kernel b7e2a5c6519adc73be55c3de2cb545e095a0fbc5.
In the Linux kernel, the following vulnerability has been resolved: bpf: Require a BPF cpumask for bpf_cpumask_populate() bpf_cpumask_populate() writes to its destination with bitmap_copy(), but the destination is typed as struct cpumask *. That allows the verifier to accept borrowed cpumask pointers returned by read-only kfuncs, such as scx_bpf_get_online_cpumask(), as a writable destination. Make the destination a struct bpf_cpumask * so populate follows the same ownership rule as the other mutating cpumask kfuncs. Query kfuncs continue to accept const struct cpumask * inputs.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=950ad93df2fce70445e655ed2e74f5c1a8653ab2 <0cfc9348a045da64955af2dd6902e66dfc7d6469, >=950ad93df2fce70445e655ed2e74f5c1a8653ab2 <8740156ad33be5071b588b594c55f279457f667c, >=950ad93df2fce70445e655ed2e74f5c1a8653ab2 <b7e2a5c6519adc73be55c3de2cb545e095a0fbc5 | 0cfc9348a045da64955af2dd6902e66dfc7d6469, 8740156ad33be5071b588b594c55f279457f667c, b7e2a5c6519adc73be55c3de2cb545e095a0fbc5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket