CVE-2026-97515i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845 On NPCM845, when a target on the I3C bus gets stuck holding SDA low, the controller reports a false Master Request (MR) in-band interrupt event. The driver handles this by emitting a STOP condition to restore the bus. However, the hardware quirk SVC_I3C_QUIRK_FALSE_SLVSTART indicates that emitting a STOP condition may spuriously set the SLVSTART interrupt status bit. In the Master Request case, this creates a feedback loop: the STOP triggers a new SLVSTART event, the IRQ handler fires again, the controller still reports an MR type, another STOP is emitted, and the cycle repeats indefinitely, resulting in an IRQ storm that can lock up the CPU. Clear the SLVSTART status bit explicitly after emitting the STOP in the Master Request IBI handler when the SVC_I3C_QUIRK_FALSE_SLVSTART quirk is set. This breaks the feedback loop without affecting normal SLVSTART processing, which is already guarded in the top-level IRQ handler by checking that MSTATUS is in SLVREQ state.
Timeline
ID reserved
By Linux
Published
- 27 days later
· 27 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1ea4653cff35c29d1dd0b14ad9c8245e7318f337 – < 335f72b1f9bbcf0f4cc5a505443b15f1af563b4f
- affected 0430bf9bc1ac068c8b8c540eb93e5751872efc51 – < e9b139c4684ed8593a0b779ca02ea05f460b2eec
- affected 0430bf9bc1ac068c8b8c540eb93e5751872efc51 – < 1effa3adfe53cb2bb28bf5640a676b791d5ab405
- affected 30748ce7e156f221fb91689b338a0d7df77b732a
- affected f2985a1de6f53abbc42c7a696ee6ba8bdecc9426
- affected 0541822045ae043d62c941ca31fa76871e436b5e
- affected d231fb443d8d4042f0dd705b93beba8c916a7344
- affected 6.12.31 – < 6.12.114
- affected 5.15.185 – < 5.16
- affected 6.1.141 – < 6.2
- affected 6.6.93 – < 6.7
- affected 6.14.9 – < 6.15
- affected 6.15
- unaffected < 6.15
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86113 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97515)Record last updated .