Kernel crash via uncleared chained interrupt handler
Published Aug 15, 2026 · Updated Aug 15, 2026
Expired pointer dereference in the Linux irqchip/ts4800 driver allows local users to crash the kernel after driver removal. ts4800_ic_remove() leaves the parent chained handler installed after its data is freed, so a later parent interrupt dereferences stale memory. Exploitation requires the TS-4800 interrupt controller to be bound and then removed before its parent interrupt fires; the documented consequence is a kernel crash.
Summary
What happened
Expired pointer dereference in the Linux irqchip/ts4800 driver allows local users to crash the kernel after driver removal. ts4800_ic_remove() leaves the parent chained handler installed after its data is freed, so a later parent interrupt dereferences stale memory. Exploitation requires the TS-4800 interrupt controller to be bound and then removed before its parent interrupt fires; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2026-72384
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-825, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.5
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <3f31f49afffa169cd01e6c37568c4df3eb1051af
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <4e8d498d32b6c67d73bb8b317ff316ff37897a3e
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <98bf7e54cec07d514b3575c11896a8b12d50ecc4
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <9ed0dca2aa05908b33ecf0bb15c7953947529542
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c
- Affected versionversion=d01f8633d52e4dac5ee598b87d49fd23346ccfd6 <e6b674dc341c6add7d85bec2ec22caf1aad35795
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo