sched_ext: Abort directly from the hardlockup handler
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3c4b38064937a761ebbf85b1649e812db85eb59e and Kernel 4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Abort directly from the hardlockup handler scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting ->aborting is exactly what breaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and drop the irq_work. This also makes the self-detected case recoverable: the perf watchdog fires on the hard-locked CPU itself, where a queued irq_work never runs with IRQs off. Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel's hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=bd2d76455b65aab77652823919db128a8e585825 <3c4b38064937a761ebbf85b1649e812db85eb59e, >=bd2d76455b65aab77652823919db128a8e585825 <4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed | 3c4b38064937a761ebbf85b1649e812db85eb59e, 4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket