CVE-2026-97515

i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845

N/A
Published: September 24, 2026 at 04:05 PM UTC
Updated: October 21, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0430bf9bc1ac068c8b8c540eb93e5751872efc510541822045ae043d62c941ca31fa76871e436b5e1ea4653cff35c29d1dd0b14ad9c8245e7318f33730748ce7e156f221fb91689b338a0d7df77b732a430bf9bc1ac68c8b8c540eb93e5751872efc515.15.185541822045ae43d62c941ca31fa76871e436b5e6.1.1416.12.316.14.96.156.6.93d231fb443d8d4042f0dd705b93beba8c916a7344f2985a1de6f53abbc42c7a696ee6ba8bdecc9426
Vendor states this is fixed in 1effa3adfe53cb2bb28bf5640a676b791d5ab405 (fixed)
Vendor states this is fixed in e9b139c4684ed8593a0b779ca02ea05f460b2eec (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.114 (unaffected)
Affected range stops below 6.13, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card