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-72384irqchip/ts4800: Fix missing chained handler cleanup on remove

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/ts4800: Fix missing chained handler cleanup on remove The driver installs a chained handler for the parent interrupt during probe using irq_set_chained_handler_and_data(), but the remove function does not clear this handler. This leaves a dangling handler that may be called when the parent interrupt fires after the driver has been removed, potentially accessing freed memory and causing a kernel crash. Additionally, the parent_irq obtained via irq_of_parse_and_map() is not stored, making it inaccessible in the remove function. Moreover, interrupt mappings created during probe are not properly disposed. Fix this by: - Saving parent_irq in probe - Clearing the chained handler with NULL in ts4800_ic_remove() - Disposing all IRQ mappings before domain removal to prevent resource leaks

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 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.21% · top 88% 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: Not scored.

Affected products

  • Linux · Linux

    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c
    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < e6b674dc341c6add7d85bec2ec22caf1aad35795
    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < 3f31f49afffa169cd01e6c37568c4df3eb1051af
    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < 4e8d498d32b6c67d73bb8b317ff316ff37897a3e
    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < 9ed0dca2aa05908b33ecf0bb15c7953947529542
    • affected d01f8633d52e4dac5ee598b87d49fd23346ccfd6 – < 98bf7e54cec07d514b3575c11896a8b12d50ecc4
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .