Vulnerability · Published Dec 22, 2025 · Assigned by Linux
CVE-2025-68333sched_ext: Fix possible deadlock in the deferred_irq_workfn()
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2025-68333 |
| Debian:13 | linux | 6.12.69-1 | DSA-6126-1 |
| Debian:14 | linux | 6.17.12-1 | DEBIAN-CVE-2025-68333 |
| Ubuntu:25.10 | linux | 6.17.0-19.19 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1009.9 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1009.9~24.04.2 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1010.10 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1010.10~24.04.1 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1009.9 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1009.9~24.04.3 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-19.19~24.04.2 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1018.18 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1017.17 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1009.9 | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1009.9~24.04.1 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1010.10 | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1008.9 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-19.19.1 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-19.19.1~24.04.1 | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-68333 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-68333 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 – before 541959b2fadb832a7d0ceb95041dc52bdcf6bff75b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 – before 600b4379b9a7ba41340d652211fb29699da4c6295b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 – before a257e974210320ede524f340ffe16bf4bf0dda1e |
| Linux | Linux | 6.12 |