Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56723: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0350d783ab888cb1cb48ced36cc28b372723f1a4, 61d590d7076b50b6ebdea1f3b83bb041c01fc482, 6ea17c03edc7ed0aabb1431eb26e2f94849af68a; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 0350d783ab888cb1cb48ced36cc28b372723f1a4, 61d590d7076b50b6ebdea1f3b83bb041c01fc482, 6ea17c03edc7ed0aabb1431eb26e2f94849af68a; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices 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.

Published
Dec 29, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-56723

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.13affected
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before 6ea17c03edc7ed0aabb1431eb26e2f94849af68aaffected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before 61d590d7076b50b6ebdea1f3b83bb041c01fc482affected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before bb6642d4b3136359b5b620049f76515876e6127eaffected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before 7ba45b8bc62e64da524d45532107ae93eb33c93caffected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before d4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62affected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before 897713c9d24f6ec394585abfcf259a6e5cad22c8affected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before b3d45c19bcffb9a9a821df759f60be39d88c19f4affected · git
    • 57129044f5044dcd73c22d91491906104bd331fd and later · before 0350d783ab888cb1cb48ced36cc28b372723f1a4affected · git
    • before 4.13not affected · semver
Affected versions · NVD (7)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.13 and later · before 5.4.287
  • linux linux kernel5.5 and later · before 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel6.2 and later · before 6.6.64
  • linux linux kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.3-16.12.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-56721Dec 29, 2024 · x86/CPU/AMD: Terminate the erratum_1386_microcode array
    28Monitor
  • ← EarlierCVE-2024-56722Dec 29, 2024 · RDMA/hns: Fix cpu stuck caused by printings during reset
    22Monitor
  • Later →CVE-2024-56724Dec 29, 2024 · mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0350d783ab888cb1cb48ced36cc28b372723f1a4Vendor (CNA)
Linux Linux61d590d7076b50b6ebdea1f3b83bb041c01fc482Vendor (CNA)
Linux Linux6ea17c03edc7ed0aabb1431eb26e2f94849af68aVendor (CNA)
Linux Linux7ba45b8bc62e64da524d45532107ae93eb33c93cVendor (CNA)
Linux Linux897713c9d24f6ec394585abfcf259a6e5cad22c8Vendor (CNA)
Linux Linuxb3d45c19bcffb9a9a821df759f60be39d88c19f4Vendor (CNA)
Linux Linuxbb6642d4b3136359b5b620049f76515876e6127eVendor (CNA)
Linux Linuxd4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records