Quick answers
- Is CVE-2026-93220 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93220 being exploited in the wild.
- How severe is CVE-2026-93220?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux v6.19 and later.
- Is there a fix for CVE-2026-93220?
- A patch was published on 2026-09-07: Fix committed and backported to stable branches Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93220 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93220?
- Check whether you run Linux at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in kick_sync_wait_bal_cb() in kernel/sched/ext/ext.c, where the function assumes execution on the runqueue's own CPU to access per-CPU snapshots safely. However, when dispatch drops the rq lock while the callback is queued, other rq lock takers (sched class change paths, scx task iterator) can flush the callback on a foreign CPU. This causes it to compare against unrelated snapshots and deadlock when the executing CPU is a wait target. The fix adds a CPU identity check that bails out if the callback runs on a foreign CPU, leaving synchronization to subsequent scheduling operations.
Affected products
- Linux Linux v6.19 and later
Timeline
- 2026-09-24: disclosed
- 2026-09-07: patched: Fix committed and backported to stable branches