# CVE-2026-72384: irqchip/ts4800: Fix missing chained handler cleanup on remove

> A missing cleanup in the ts4800 irqchip driver allows a use-after-free condition, potentially causing kernel crashes or code execution upon driver removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72384, DEBIAN-CVE-2026-72384, GHSA-xcpr-v9rp-m43f, UBUNTU-CVE-2026-72384

## What is CVE-2026-72384?

CVE-2026-72384 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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

## Which versions are affected by CVE-2026-72384?


## How do I fix CVE-2026-72384?

Apply the vendor's patch.

## Is CVE-2026-72384 being exploited?

There is no known exploitation of CVE-2026-72384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72384 and fix it if it is affected.

What it is: CVE-2026-72384 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72384 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72384/ (Markdown: https://insights.sbomify.com/CVE-2026-72384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72384
- OSV: https://osv.dev/vulnerability/CVE-2026-72384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72384/
Summaries are generated and may contain mistakes; the official description above is the record.