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.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2025-12-22 17:16
Updated : 2026-02-26 15:53
NVD link : CVE-2025-68333
Mitre link : CVE-2025-68333
CVE.ORG link : CVE-2025-68333
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking
