CVE-2026-72384 json
irqchip/ts4800: Fix missing chained handler cleanup on remove
published 2026-08-15 2 mo ago modified 2026-08-17 2 mo ago also EUVD-2026-59283
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72384
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gke Ubuntu 24.04 LTS 6.8.0-1066.74
- linux-gke Ubuntu 26.04 LTS 7.0.0-1008.9
ubuntu advisories UBUNTU-CVE-2026-72384
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c commit
- git.kernel.org/stable/c/e6b674dc341c6add7d85bec2ec22caf1aad35795 commit
- git.kernel.org/stable/c/3f31f49afffa169cd01e6c37568c4df3eb1051af commit
- git.kernel.org/stable/c/4e8d498d32b6c67d73bb8b317ff316ff37897a3e commit
- git.kernel.org/stable/c/9ed0dca2aa05908b33ecf0bb15c7953947529542 commit
- git.kernel.org/stable/c/98bf7e54cec07d514b3575c11896a8b12d50ecc4 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72384 updated cvss 5.5
kernel: irqchip/ts4800: Fix missing chained handler cleanup on remove
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c
- git.kernel.org /stable/c/e6b674dc341c6add7d85bec2ec22caf1aad35795
- git.kernel.org /stable/c/3f31f49afffa169cd01e6c37568c4df3eb1051af
- git.kernel.org /stable/c/4e8d498d32b6c67d73bb8b317ff316ff37897a3e
- git.kernel.org /stable/c/9ed0dca2aa05908b33ecf0bb15c7953947529542
- git.kernel.org /stable/c/98bf7e54cec07d514b3575c11896a8b12d50ecc4
Sources
- CVE List CVE-2026-72384
- NVD CVE-2026-72384
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.