CVE-2026-72384

Received Received - Intake

irqchip/ts4800 Chained Handler Cleanup Flaw

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-17

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-72384

EUVD

EUVD-2026-59283

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's irqchip/ts4800 driver. During setup, the driver sets up a chained interrupt handler for the parent interrupt but fails to remove it properly when the driver is unloaded. This leaves a dangling handler that could be called after the driver's memory is freed, potentially causing a kernel crash due to accessing invalid memory.

Detection Guidance

This vulnerability is specific to the Linux kernel's ts4800 interrupt controller driver. Detection requires checking kernel logs for crashes or warnings related to interrupt handling in the ts4800 driver. Look for messages about dangling handlers or kernel oops after driver removal. No direct network detection is applicable.

Impact Analysis

If exploited, this flaw could lead to system instability or crashes when the affected driver is removed while interrupts are still active. It may cause kernel panics, data corruption, or denial-of-service conditions on systems using the ts4800 interrupt controller.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a kernel-level interrupt handling issue that could lead to system crashes but does not involve data exposure, unauthorized access, or privacy violations typically addressed by these regulations.

Mitigation Strategies

Apply the kernel patch that fixes the ts4800 driver's interrupt handler cleanup. Update to a Linux kernel version containing the fix. If immediate patching is not possible, avoid unloading or removing the ts4800 driver until patched.

Hi! I’m here to help you understand CVE-2026-72384. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70