CVE-2026-72384
CVE CVE-2026-72384EUVD EUVD-2026-59283Published 2026-08-15T05:56:15.000ZLast changed 2026-08-17T05:13:37.000Z
What the advisory describes
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
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c; patch: 6.1.178; d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <3f31f49afffa169cd01e6c37568c4df3eb1051af; patch: 6.6.145; d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <98bf7e54cec07d514b3575c11896a8b12d50ecc4; d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <e6b674dc341c6add7d85bec2ec22caf1aad35795; patch: 7.2; 4.5; patch: 0; patch: 6.18.40; d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <4e8d498d32b6c67d73bb8b317ff316ff37897a3e; patch: 7.1.5; d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <9ed0dca2aa05908b33ecf0bb15c7953947529542; patch: 6.12.97
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.