CVE-2026-72384
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
Affected versions
Linux kernel versions
4.5
and later are affected. Fixed in
6.1.178,
6.6.145,
6.12.97,
6.18.40,
7.1.5,
7.2-rc2
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-72384?
CVE-2026-72384 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.5 onward and has been patched in 6.1.178, 6.6.145, 6.12.97 and others. CVE-2026-72384 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-72384?
Yes. CVE-2026-72384 has been patched. Fixed versions include 6.1.178, 6.6.145, 6.12.97 and others. If you are running Linux kernel 4.5 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-72384 actively exploited?
No. CVE-2026-72384 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.