irqchip/renesas-irqc: Fix generic interrupt chip leak on remove (CVE-2026-93072) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93072

irqchip/renesas-irqc: Fix generic interrupt chip leak on remove

Answer in brief

CVE-2026-93072 records a Unknown severity vulnerability in irqchip/renesas-irqc: Fix generic interrupt chip leak on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=99c221df33fbfa1b30e15dee879eb0a9ae1be353 <3d39757ef791f90028da9c8b7c1fbbb497237e58 \|\| >=99c221df33fbfa1b30e15dee879eb0a9ae1be353 <4bf7614d048434326081eef0ebef33cb77fe2ffc \|\| >=99c221df33fbfa1b30e15dee879eb0a9ae1be353 <9acc996cb2e8477ae81bd7c067fec15202d6bc89 \|\| >=99c221df33fbfa1b30e15dee879eb0a9ae1be353 <7c614f83301d464e2fb498d63552490d137ea10d \|\| >=99c221df33fbfa1b30e15dee879eb0a9ae1be353 <616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba	3d39757ef791f90028da9c8b7c1fbbb497237e58, 4bf7614d048434326081eef0ebef33cb77fe2ffc, 9acc996cb2e8477ae81bd7c067fec15202d6bc89, 7c614f83301d464e2fb498d63552490d137ea10d, 616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba
Linux/Linuxgeneric	4.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 3d39757ef791f90028da9c8b7c1fbbb497237e58 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.