CVE-2024-56724 json
mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
published last yr. modified 4mo ago also EUVD-2024-53372
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ).
Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them.
Patch / fix
- Linux Linux 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2, 6.13
- linux Debian 12 6.1.123-1
- linux Debian 14, Debian 13 6.12.3-1
debian advisories DEBIAN-CVE-2024-56724
- linux Ubuntu 20.04 LTS 5.4.0-211.231
- linux Ubuntu 22.04 LTS 5.15.0-135.146
- linux Ubuntu 24.04 LTS 6.8.0-58.60
- linux-aws Ubuntu 20.04 LTS 5.4.0-1142.152
- linux-aws Ubuntu 22.04 LTS 5.15.0-1080.87
- linux-aws Ubuntu 24.04 LTS 6.8.0-1027.29
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1145.154
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1079.88
ubuntu advisories UBUNTU-CVE-2024-56724
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-livepatch-MICRO-6-0-RT_Update_5 Linux Micro 6.1, Linux Micro 6.0 1-1.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-24.1.21.4
- kernel-livepatch-MICRO-6-0_Update_5 Linux Micro 6.1, Linux Micro 6.0 1-1.2
suse advisories SUSE-SU-2025:20166-1SUSE-SU-2025:20249-1SUSE-SU-2025:20165-1SUSE-SU-2025:20248-1SUSE-SU-2025:0557-1SUSE-SU-2025:0499-1
- kernel CBL-Mariner 2.0 5.15.176.3-1
- kernel Azure Linux 3.0 6.6.64.2-1
azure linux advisories AZL-55268AZL-55271
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/b7c7c400de85d915e0da7c2c363553a801c47349 commit
- git.kernel.org/stable/c/c472b55cc0bc3df805db6a14f50a084884cf18ee commit
- git.kernel.org/stable/c/da498e02c92e6d82df8001438dd583b90c570815 commit
- git.kernel.org/stable/c/56acf415772ee7e10e448b371f52b249aa2d0f7b commit
- git.kernel.org/stable/c/1b734ad0e33648c3988c6a37c2ac16c2d63eda06 commit
- git.kernel.org/stable/c/2310f5336f32eac9ada2d59b965d578efe25c4bf commit
- git.kernel.org/stable/c/5bc6d0da4a32fe34a9960de577e0b7de3454de0c commit
- git.kernel.org/stable/c/9b79d59e6b2b515eb9a22bc469ef7b8f0904fc73 commit
Is CVE-2024-56724 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-56724 updated cvss 5.5
kernel: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
cisa ICSA-25-226-07 updated cvss 5.5
Siemens Third-Party Components in SINEC OS
-
Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) < 3.2affected: fixed in V3.2 support.industry.siemens.com
-
Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family < 3.2affected: fixed in V3.2
-
Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family < 3.2affected: fixed in V3.2 support.industry.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/b7c7c400de85d915e0da7c2c363553a801c47349
patch
-
git.kernel.org
/stable/c/c472b55cc0bc3df805db6a14f50a084884cf18ee
patch
-
git.kernel.org
/stable/c/da498e02c92e6d82df8001438dd583b90c570815
patch
-
git.kernel.org
/stable/c/56acf415772ee7e10e448b371f52b249aa2d0f7b
patch
-
git.kernel.org
/stable/c/1b734ad0e33648c3988c6a37c2ac16c2d63eda06
patch
-
git.kernel.org
/stable/c/2310f5336f32eac9ada2d59b965d578efe25c4bf
patch
-
git.kernel.org
/stable/c/5bc6d0da4a32fe34a9960de577e0b7de3454de0c
patch
-
git.kernel.org
/stable/c/9b79d59e6b2b515eb9a22bc469ef7b8f0904fc73
patch
- lists.debian.org /debian-lts-announce/2025/03/msg00001.html
- lists.debian.org /debian-lts-announce/2025/03/msg00002.html
Sources
- CVE List CVE-2024-56724
- NVD CVE-2024-56724
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.