Kernel panic via stale NPCM I2C interrupts
Published Mar 27, 2025 · Updated May 11, 2026
Denial of service in the Linux NPCM I2C driver allows local users to trigger a kernel panic after a warm BMC reboot. The probe path registers its IRQ handler while a retained, read-only I2C status remains interrupt-enabled, causing the handler to fire continuously. Reachability requires an NPCM-based BMC to reboot during an I2C transmit transfer; the soft-lockup watchdog then panics and reboots the kernel.
Summary
What happened
Denial of service in the Linux NPCM I2C driver allows local users to trigger a kernel panic after a warm BMC reboot. The probe path registers its IRQ handler while a retained, read-only I2C status remains interrupt-enabled, causing the handler to fire continuously. Reachability requires an NPCM-based BMC to reboot during an I2C transmit transfer; the soft-lockup watchdog then panics and reboots the kernel.
The record
- CVE
- CVE-2025-21878
- Published
- Mar 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <12d0e39916705b68d2d8ba20a8e35d1d27afc260
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <1b267e1b87d52b16e7dfcc7ab2ab760f6f8f9ca9
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <545b563eb00d0576775da4011b3f7ffefc9e8c60
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <846e371631c57365eeb89e5db1ab0f344169af93
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <dd1998e243f5fa25d348a384ba0b6c84d980f2b2
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <e3aea1dba97d31eceed7b622000af0406988b9c8
- Affected versionversion=56a1485b102ed1cd5a4af8e87ed794699fd1cad2 <f32d7b4dc6e791523c70e83049645dcba2a2aa33
- Affected versionversion=5.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo