CVE-2026-97515: Linux kernel · i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e9b139c4684ed8593a0b779ca02ea05f460b2eec : patch Linux kernel soon.
Data as of 26 Oct 2026, 20:13 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 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e9b139c4684ed8593a0b779ca02ea05f460b2eec, 335f72b1f9bbcf0f4cc5a505443b15f1af563b4f, 6.15 +5
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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in Linux kernel versions 6.15, 6.12.114, 6.7, 6.2, 5.16, and later. Users and administrators should upgrade to these or later kernel versions to mitigate the issue. No additional mitigation steps are required as the fix addresses the root cause.
Description
A vulnerability in the Linux kernel's I3C master controller on NPCM845 hardware can cause an interrupt request (IRQ) storm due to a feedback loop triggered by a false SLVSTART interrupt status bit. This occurs when a target device holds the SDA line low, causing the controller to emit repeated STOP conditions and lock up the CPU. The issue has been fixed by explicitly clearing the SLVSTART status bit after emitting the STOP condition in affected kernel versions.