sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0102989af4c334d1d98b2a0fd4d61a5152e39b72, Kernel 255dd31bfc4a67a19b1fc2cd130a50284dadfe3a and Kernel 428dc9fc0873989d73918d4a9cc22745b7bbc799.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator BPF programs may call next() and destroy() on BPF iterators even after new() returns an error value (e.g. bpf_for_each() macro ignores error returns from new()). bpf_iter_scx_dsq_new() could leave the iterator in an uninitialized state after an error return causing bpf_iter_scx_dsq_next() to dereference garbage data. Make bpf_iter_scx_dsq_new() always clear $kit->dsq so that next() and destroy() become noops.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.12, >=650ba21b131ed1f8ee57826b2c6295a3be221132 <0102989af4c334d1d98b2a0fd4d61a5152e39b72, >=650ba21b131ed1f8ee57826b2c6295a3be221132 <255dd31bfc4a67a19b1fc2cd130a50284dadfe3a, >=650ba21b131ed1f8ee57826b2c6295a3be221132 <428dc9fc0873989d73918d4a9cc22745b7bbc799 | 0102989af4c334d1d98b2a0fd4d61a5152e39b72, 255dd31bfc4a67a19b1fc2cd130a50284dadfe3a, 428dc9fc0873989d73918d4a9cc22745b7bbc799 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket