CVE-2026-45919: Linux kernel · sched/rt: Skip currently executing CPU in rto_next_cpu()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d57d0746276a88ea43a2cc62b849fd8a95e32e41 : patch Linux kernel soon.
Data as of 6 Nov 2026, 16:05 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d57d0746276a88ea43a2cc62b849fd8a95e32e41, a6a73403733e86748421f2eeaf028c85683ef896, 94894c9c477e53bcea052e075c53f89df3d2a33e +8
Exploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 4.5, 4.10, 4.15, and corresponding commits. Users and administrators should upgrade affected Linux kernel versions to these fixed releases to prevent CPU hardlockup caused by this issue.
Description
A vulnerability in the Linux kernel scheduler's real-time load balancing causes CPU0 to enter an infinite self-interrupt loop under specific task scheduling conditions, leading to a CPU hardlockup. The issue arises when CPU0 is overloaded with certain real-time and CFS tasks, and other CPUs trigger real-time load balancing with HAVE_RT_PUSH_IPI enabled. This results in repeated self-IPIs on CPU0, causing a hardlockup. The flaw is fixed by modifying rto_next_cpu() to skip the currently executing CPU, preventing redundant self-IPIs.
References
- git.kernel.org/stable/c/d57d0746276a88ea43a2cc62b849fd8a95e32e41 (opens in a new tab)
- git.kernel.org/stable/c/3b3c672a66db3de3b40f8a7057864bc1f874ede3 (opens in a new tab)
- git.kernel.org/stable/c/16ca9f3117e9a294646c897daf08a5ab546c711b (opens in a new tab)
- git.kernel.org/stable/c/8ad5577b2d4acfd83f03d97a0aece2d18aac5f07 (opens in a new tab)
- git.kernel.org/stable/c/a6a73403733e86748421f2eeaf028c85683ef896 (opens in a new tab)
- git.kernel.org/stable/c/52aeb1e07ec223caf212f036817976c98d2aa250 (opens in a new tab)
- git.kernel.org/stable/c/9f25edc5a20cb52a5abbf25f0724bb4732b81801 (opens in a new tab)
- git.kernel.org/stable/c/94894c9c477e53bcea052e075c53f89df3d2a33e (opens in a new tab)