Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-56691mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 17 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-56691, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 0997e77c51330c2866a4f39480e762cca92ad953
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 0b648968bfa4f5c9c4983bca9f2de17626ed6fb6
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 23230ac3c5ca3f154b64849d1cf50583b4e6b98c
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < c310e6916c0b297011d0fec03f168a6b24e9e984
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < e1ef62e8d262e3f27446d26742208c1c81e9ee18
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 518e414d24e7037d6cc7198e942bf47fe6f5e8e1
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 87a07a5b0b296e489c606ca95ffc16c18821975b
    • affected 9c6235c8633210cc2da0882e2e9d6ff90aa37503 – < 686fb77712a4bc94b76a0c5ae74c60118b7a0d79
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.4.287 – ≤ 5.4.*
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.64 – ≤ 6.6.*
    • unaffected 6.11.11 – ≤ 6.11.*
    • unaffected 6.12.2 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-56691 badge
[![CVE-2024-56691](https://cveledger.app/badge/CVE-2024-56691.svg)](https://cveledger.app/cve/CVE-2024-56691)

Record last updated .