CVE-2026-72384

What the bug is

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

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/irqchip/irq-ts4800.c

What this is

IRQCHIP DRIVERSMAINTAINERS section matched on drivers/irqchip/ · linux-kernel@vger.kernel.org · Maintained

Kernel module

none to look for. The file would have gone into irq_ts4800, and Debian does not compile it into that module, so finding irq_ts4800 in lsmod would say nothing about this CVE.

Check it on the machine

grep -w CONFIG_TS4800_IRQ /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sidn

n

not enabled on any flavour - this release does not build the code

Build switch

CONFIG_TS4800_IRQ

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-08-15 (2 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.21%, higher than 11.0% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/irqchip

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
4.5	6.1.178	b5b2b2cb6a91
4.5	6.6.145	e6b674dc341c
4.5	6.12.97	3f31f49afffa
4.5	6.18.40	4e8d498d32b6
4.5	7.1.5	9ed0dca2aa05
4.5	7.2	98bf7e54cec0