Strix
56.4K

CVE-2026-72384

UnknownEPSS 0.21%

Last modified

CVE-2026-72384 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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

Metrics

EPSS Probability
0.21%

11.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c; >= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < e6b674dc341c6add7d85bec2ec22caf1aad35795; >= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < 3f31f49afffa169cd01e6c37568c4df3eb1051af; >= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < 4e8d498d32b6c67d73bb8b317ff316ff37897a3e; >= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < 9ed0dca2aa05908b33ecf0bb15c7953947529542; >= d01f8633d52e4dac5ee598b87d49fd23346ccfd6, < 98bf7e54cec07d514b3575c11896a8b12d50ecc4
LinuxLinux4.5

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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
How severe is CVE-2026-72384?
Severity scoring for CVE-2026-72384 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72384?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72384?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST