CVE-2025-68333: sched_ext: Fix possible deadlock in the deferred_irq_workfn()
In the Linux kernel, the following vulnerability has been resolved:
schedext: Fix possible deadlock in the deferredirqworkfn()
For PREEMPTRT=y kernels, the deferredirqworkfn() is executed in the per-cpu irqwork/ task context and not disable-irq, if the rq returned by containerof() is current CPU's rq, the following scenarios may occur:
lock(&rq->lock); <Interrupt> lock(&rq->lock);
This commit use IRQWORKINITHARD() to replace initirqwork() to initialize rq->scx.deferredirqwork, make the deferredirqworkfn() is always invoked in hard-irq context.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68333?
CVE-2025-68333 has a severity rating that indicates a significant impact on system reliability due to possible deadlock scenarios.
How do I fix CVE-2025-68333?
To fix CVE-2025-68333, update your Linux kernel to the latest stable version where this vulnerability has been resolved.
Which versions of the Linux Kernel are affected by CVE-2025-68333?
CVE-2025-68333 affects versions of the Linux kernel that utilize PREEMPT_RT=y configurations.
What is the nature of the issue in CVE-2025-68333?
The issue in CVE-2025-68333 involves a possible deadlock condition in the deferred_irq_workfn() execution.
Are there any workarounds for CVE-2025-68333?
Currently, the recommended approach for CVE-2025-68333 is to apply the official kernel patch rather than use workarounds.