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-2026-93072

irqchip/renesas-irqc: Fix generic interrupt chip leak on remove

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/renesas-irqc: Fix generic interrupt chip leak on remove The driver allocates domain generic chips probe. However, on driver removal, the generic chips are not automatically freed when the interrupt domain is removed because the domain flags do not include IRQ_DOMAIN_FLAG_DESTROY_GC. This causes both the domain generic chips structure and the associated generic chips to be leaked. Additionally, the generic chips remain on the global list and may later be accessed by generic interrupt chip suspend, resume, or shutdown callbacks after the driver has been removed, potentially resulting in a use-after-free and kernel crash. Fix the resource leak by setting IRQ_DOMAIN_FLAG_DESTROY_GC on the interrupt domain; this lets the interrupt domain core automatically release all generic chips when irq_domain_remove() is invoked, removing the need for manual cleanup calls in error paths and remove callback.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 99c221df33fbfa1b30e15dee879eb0a9ae1be353 – < 3d39757ef791f90028da9c8b7c1fbbb497237e58
    • affected 99c221df33fbfa1b30e15dee879eb0a9ae1be353 – < 4bf7614d048434326081eef0ebef33cb77fe2ffc
    • affected 99c221df33fbfa1b30e15dee879eb0a9ae1be353 – < 9acc996cb2e8477ae81bd7c067fec15202d6bc89
    • affected 99c221df33fbfa1b30e15dee879eb0a9ae1be353 – < 7c614f83301d464e2fb498d63552490d137ea10d
    • affected 99c221df33fbfa1b30e15dee879eb0a9ae1be353 – < 616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .