CVE-2026-72384

irqchip/ts4800: Fix missing chained handler cleanup on remove

N/A
Published: August 15, 2026 at 05:56 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.5 ≤ v < 6.1.1784.5 ≤ v < 6.12.974.5 ≤ v < 6.18.404.5 ≤ v < 6.6.1454.5 ≤ v < 7.1.54.5 ≤ v < 7.24.5d01f8633d52e4dac5ee598b87d49fd23346ccfd6
Vendor states this is fixed in 3f31f49afffa169cd01e6c37568c4df3eb1051af (fixed)
Vendor states this is fixed in 4e8d498d32b6c67d73bb8b317ff316ff37897a3e (fixed)
Vendor states this is fixed in 98bf7e54cec07d514b3575c11896a8b12d50ecc4 (fixed)
Vendor states this is fixed in 9ed0dca2aa05908b33ecf0bb15c7953947529542 (fixed)
Vendor states this is fixed in b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c (fixed)
Vendor states this is fixed in e6b674dc341c6add7d85bec2ec22caf1aad35795 (fixed)
Vendor states this is fixed in 4.5 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card