CVE-2026-93220: Linux kernel · sched_ext: Keep kick_sync waiting on the rq's own CPU
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to e0253dd04beb03e79477c5ef4768b11135687206 or c736ea0fe7b4df920da6bd43a81c5eeecadcc8be soon.
Data as of 26 Oct 2026, 14:33 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e0253dd04beb03e79477c5ef4768b11135687206, c736ea0fe7b4df920da6bd43a81c5eeecadcc8be
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to e0253dd04beb03e79477c5ef4768b11135687206 or c736ea0fe7b4df920da6bd43a81c5eeecadcc8be.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The issue is fixed in the Linux kernel commits e0253dd04beb03e79477c5ef4768b11135687206 and c736ea0fe7b4df920da6bd43a81c5eeecadcc8be. Users should update to a Linux kernel version including these fixes or later. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel scheduler (version 6.19) involves the kick_sync_wait_bal_cb() callback running on a CPU different from the runqueue's own CPU. This can cause deadlocks due to comparing unrelated snapshots and improper wait state handling. The issue has been fixed in specific commits.