Local denial of service via IRQ misrouting
Published Dec 28, 2024 · Updated May 11, 2026
Incorrect IRQ-domain handling in Linux kernels beginning with 4.9 allows local users to cause a denial of service on supported hardware. The MFD parent creates Whiskey Cove USB Type-C children without the charger IRQ domain, so platform_get_irq() receives IRQ 0 instead of a mapped Linux vIRQ. Reachability requires the Intel BXT Whiskey Cove PMIC USB Type-C driver; public sources do not identify the user action that triggers failure.
Summary
What happened
Incorrect IRQ-domain handling in Linux kernels beginning with 4.9 allows local users to cause a denial of service on supported hardware. The MFD parent creates Whiskey Cove USB Type-C children without the charger IRQ domain, so platform_get_irq() receives IRQ 0 instead of a mapped Linux vIRQ. Reachability requires the Intel BXT Whiskey Cove PMIC USB Type-C driver; public sources do not identify the user action that triggers failure.
The record
- CVE
- CVE-2024-56691
- Published
- Dec 28, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2024CVE 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=4.9
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <0997e77c51330c2866a4f39480e762cca92ad953
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <0b648968bfa4f5c9c4983bca9f2de17626ed6fb6
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <23230ac3c5ca3f154b64849d1cf50583b4e6b98c
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <518e414d24e7037d6cc7198e942bf47fe6f5e8e1
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <686fb77712a4bc94b76a0c5ae74c60118b7a0d79
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <87a07a5b0b296e489c606ca95ffc16c18821975b
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <c310e6916c0b297011d0fec03f168a6b24e9e984
- Affected versionversion=9c6235c8633210cc2da0882e2e9d6ff90aa37503 <e1ef62e8d262e3f27446d26742208c1c81e9ee18
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.
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