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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-6126-1 | linux security update |
Ubuntu USN |
USN-8094-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8094-2 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8094-3 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-8094-4 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-8094-5 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-8152-1 | Linux kernel (OEM) vulnerabilities |
Thu, 26 Feb 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-667 | |
| CPEs | cpe:2.3:o:linux:linux_kernel:6.18:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.18:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:* |
|
| Metrics |
cvssV3_1
|
Fri, 30 Jan 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 23 Dec 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 22 Dec 2025 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | sched_ext: Fix possible deadlock in the deferred_irq_workfn() | |
| First Time appeared |
Linux
Linux linux Kernel |
|
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Linux
Linux linux Kernel |
|
| References |
|
Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2026-05-11T21:51:09.677Z
Reserved: 2025-12-16T14:48:05.297Z
Link: CVE-2025-68333
No data.
Status : Analyzed
Published: 2025-12-22T17:16:01.020
Modified: 2026-02-26T15:53:10.370
Link: CVE-2025-68333
OpenCVE Enrichment
No data.
Debian DSA
Ubuntu USN