# CVE-2026-92524: irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc()

> A resource leak in the Linux kernel's GICv3 ITS driver can lead to denial of service when interrupt allocation fails.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-102741, BELL-CVE-2026-92524, DEBIAN-CVE-2026-92524, GHSA-gw35-7q98-xvfh, UBUNTU-CVE-2026-92524

## What is CVE-2026-92524?

CVE-2026-92524 is a denial of service 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/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc()

When its_irq_gic_domain_alloc() fails, the following
its_vpe_irq_domain_free() fails to invoke its_vep_teardown() for the
corresponding interrupt, which leaks the resource.

Invoke its_vpe_teardown() in the error handling path to avoid the leak.

[ tglx: Massaged change log ]

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


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

Apply the vendor's patch.

## Is CVE-2026-92524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92524 is a denial of service 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-92524 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-92524/ (Markdown: https://insights.sbomify.com/CVE-2026-92524/index.md)
```

## Sources

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

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