# CVE-2026-93072: irqchip/renesas-irqc: Fix generic interrupt chip leak on remove

> A use-after-free in the Renesas IRQC driver can cause a kernel crash when the driver is removed, requiring local privileged access to trigger.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102342, BELL-CVE-2026-93072, DEBIAN-CVE-2026-93072, GHSA-h6q6-g8xj-rf6w, UBUNTU-CVE-2026-93072

## What is CVE-2026-93072?

CVE-2026-93072 is an use after free vulnerability in Linux, published on 17 Sep 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/renesas-irqc: Fix generic interrupt chip leak on remove

The driver allocates domain generic chips probe. However, on driver
removal, the generic chips are not automatically freed when the interrupt
domain is removed because the domain flags do not include
IRQ_DOMAIN_FLAG_DESTROY_GC.

This causes both the domain generic chips structure and the associated
generic chips to be leaked. Additionally, the generic chips remain on the
global list and may later be accessed by generic interrupt chip suspend,
resume, or shutdown callbacks after the driver has been removed,
potentially resulting in a use-after-free and kernel crash.

Fix the resource leak by setting IRQ_DOMAIN_FLAG_DESTROY_GC on the
interrupt domain; this lets the interrupt domain core automatically
release all generic chips when irq_domain_remove() is invoked, removing
the need for manual cleanup calls in error paths and remove callback.

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


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

Apply the vendor's patch.

## Is CVE-2026-93072 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93072 is an use after free vulnerability in Linux, published on 17 Sep 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-93072 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-93072/ (Markdown: https://insights.sbomify.com/CVE-2026-93072/index.md)
```

## Sources

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

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