Local denial of service via TMU IRQ misrouting
Published Dec 29, 2024 · Updated May 11, 2026
Improper IRQ handling in the Linux kernel's Intel BXTWC TMU driver allows local users to cause a denial of service. The TMU probe obtains an IRQ from the wrong MFD interrupt domain and remaps the already resolved platform IRQ through regmap_irq_get_virq(), potentially producing IRQ 0 and a kernel WARN(). The condition requires Intel Whiskey Cove PMIC TMU hardware, and public records do not identify how a local user reaches the probe path.
Summary
What happened
Improper IRQ handling in the Linux kernel's Intel BXTWC TMU driver allows local users to cause a denial of service. The TMU probe obtains an IRQ from the wrong MFD interrupt domain and remaps the already resolved platform IRQ through regmap_irq_get_virq(), potentially producing IRQ 0 and a kernel WARN(). The condition requires Intel Whiskey Cove PMIC TMU hardware, and public records do not identify how a local user reaches the probe path.
The record
- CVE
- CVE-2024-56724
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 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.10
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <1b734ad0e33648c3988c6a37c2ac16c2d63eda06
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <2310f5336f32eac9ada2d59b965d578efe25c4bf
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <56acf415772ee7e10e448b371f52b249aa2d0f7b
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <5bc6d0da4a32fe34a9960de577e0b7de3454de0c
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <9b79d59e6b2b515eb9a22bc469ef7b8f0904fc73
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <b7c7c400de85d915e0da7c2c363553a801c47349
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <c472b55cc0bc3df805db6a14f50a084884cf18ee
- Affected versionversion=957ae5098185e763b5c06be6c3b4b6e98c048712 <da498e02c92e6d82df8001438dd583b90c570815
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
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