Answer in brief
CVE-2026-72384 records a Unknown severity vulnerability in irqchip/ts4800: Fix missing chained handler cleanup on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <e6b674dc341c6add7d85bec2ec22caf1aad35795 || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <3f31f49afffa169cd01e6c37568c4df3eb1051af || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <4e8d498d32b6c67d73bb8b317ff316ff37897a3e || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <9ed0dca2aa05908b33ecf0bb15c7953947529542 || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <98bf7e54cec07d514b3575c11896a8b12d50ecc4 | b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c, e6b674dc341c6add7d85bec2ec22caf1aad35795, 3f31f49afffa169cd01e6c37568c4df3eb1051af, 4e8d498d32b6c67d73bb8b317ff316ff37897a3e, 9ed0dca2aa05908b33ecf0bb15c7953947529542, 98bf7e54cec07d514b3575c11896a8b12d50ecc4 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72384 records a Unknown severity vulnerability in irqchip/ts4800: Fix missing chained handler cleanup on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <e6b674dc341c6add7d85bec2ec22caf1aad35795 || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <3f31f49afffa169cd01e6c37568c4df3eb1051af || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <4e8d498d32b6c67d73bb8b317ff316ff37897a3e || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <9ed0dca2aa05908b33ecf0bb15c7953947529542 || >=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <98bf7e54cec07d514b3575c11896a8b12d50ecc4 | b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c, e6b674dc341c6add7d85bec2ec22caf1aad35795, 3f31f49afffa169cd01e6c37568c4df3eb1051af, 4e8d498d32b6c67d73bb8b317ff316ff37897a3e, 9ed0dca2aa05908b33ecf0bb15c7953947529542, 98bf7e54cec07d514b3575c11896a8b12d50ecc4 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.