Local service interruption via incorrect IRQ-domain assignment
Published Dec 29, 2024 · Updated May 11, 2026
Improper IRQ-domain handling in Linux allows local users to interrupt service on systems using Intel BXTWC PMIC devices. The intel_soc_pmic_bxtwc driver registers multiple MFD children without assigning each child the IRQ domain for its own regmap IRQ chip, so IRQ resource zero is treated as a Linux vIRQ. Reachability requires local low-privilege access and compatible PMIC hardware; the consequence is limited to service interruption, with no reported data exposure or modification.
Summary
What happened
Improper IRQ-domain handling in Linux allows local users to interrupt service on systems using Intel BXTWC PMIC devices. The intel_soc_pmic_bxtwc driver registers multiple MFD children without assigning each child the IRQ domain for its own regmap IRQ chip, so IRQ resource zero is treated as a Linux vIRQ. Reachability requires local low-privilege access and compatible PMIC hardware; the consequence is limited to service interruption, with no reported data exposure or modification.
The record
- CVE
- CVE-2024-56723
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- 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.13
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <0350d783ab888cb1cb48ced36cc28b372723f1a4
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <61d590d7076b50b6ebdea1f3b83bb041c01fc482
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <6ea17c03edc7ed0aabb1431eb26e2f94849af68a
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <7ba45b8bc62e64da524d45532107ae93eb33c93c
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <897713c9d24f6ec394585abfcf259a6e5cad22c8
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <b3d45c19bcffb9a9a821df759f60be39d88c19f4
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <bb6642d4b3136359b5b620049f76515876e6127e
- Affected versionversion=57129044f5044dcd73c22d91491906104bd331fd <d4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62
What conditions does exploitation require?
What is affected?
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