sched_ext: Fix possible deadlock in the deferred_irq_workfn()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 541959b2fadb832a7d0ceb95041dc52bdcf6bff7, Kernel 600b4379b9a7ba41340d652211fb29699da4c629 and Kernel a257e974210320ede524f340ffe16bf4bf0dda1e.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix possible deadlock in the deferred_irq_workfn() For PREEMPT_RT=y kernels, the deferred_irq_workfn() is executed in the per-cpu irq_work/* task context and not disable-irq, if the rq returned by container_of() is current CPU's rq, the following scenarios may occur: lock(&rq->__lock); <Interrupt> lock(&rq->__lock); This commit use IRQ_WORK_INIT_HARD() to replace init_irq_work() to initialize rq->scx.deferred_irq_work, make the deferred_irq_workfn() is always invoked in hard-irq context.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.12, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <541959b2fadb832a7d0ceb95041dc52bdcf6bff7, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <600b4379b9a7ba41340d652211fb29699da4c629, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <a257e974210320ede524f340ffe16bf4bf0dda1e | 541959b2fadb832a7d0ceb95041dc52bdcf6bff7, 600b4379b9a7ba41340d652211fb29699da4c629, a257e974210320ede524f340ffe16bf4bf0dda1e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket