IPMI driver hang via repeated KCS recovery
Published Nov 12, 2025 · Updated May 11, 2026
Infinite loop in the Linux kernel IPMI KCS driver allows a misbehaving BMC to keep error recovery running indefinitely. When a KCS interface becomes hosed, the regressing code reinitializes its state to KCS_ERROR0 and resets retry bookkeeping instead of returning it to idle, so a partially responsive BMC restarts recovery without an effective stop. Reachability requires an enabled KCS-based IPMI interface and a BMC that responds enough to enter recovery but cannot complete the transaction; the loop can monopolize the IPMI polling path and prevent management operations from completing.
Summary
What happened
Infinite loop in the Linux kernel IPMI KCS driver allows a misbehaving BMC to keep error recovery running indefinitely. When a KCS interface becomes hosed, the regressing code reinitializes its state to KCS_ERROR0 and resets retry bookkeeping instead of returning it to idle, so a partially responsive BMC restarts recovery without an effective stop. Reachability requires an enabled KCS-based IPMI interface and a BMC that responds enough to enter recovery but cannot complete the transaction; the loop can monopolize the IPMI polling path and prevent management operations from completing.
The record
- CVE
- CVE-2025-40192
- Published
- Nov 12, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 12, 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=6.2
- Affected versionversion=c608966f3f9c2dca596967501d00753282b395fc <5d09ee1bec870263f4ace439402ea840503b503b
- Affected versionversion=c608966f3f9c2dca596967501d00753282b395fc <8cf5c24533b8058910fcb83a25a9cf0306383780
- Affected versionversion=c608966f3f9c2dca596967501d00753282b395fc <b9cc7155e65f6feca51bfedd543b9bd300e2be2b
- Affected versionversion=c608966f3f9c2dca596967501d00753282b395fc <f4aab940ae9eb3ba32e5332b35703673f00d7f37
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
No sourced classifications are available.
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