irqchip/ts4800: Fix missing chained handler cleanup on remove
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d01f8633d52e4dac5ee598b87d49fd23346ccfd6 · < 98bf7e54cec07d514b3575c11896a8b12d50ecc4| No fix yet |
| Linux Linux |
|
|
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
From the CVE record · Linux
The Linux kernel's ts4800 interrupt controller driver can leave a chained handler in place after the driver is removed. If the parent interrupt fires afterward, the handler may access freed memory and crash the kernel. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the ts4800 interrupt controller driver should check their deployments; affected versions are not specified.