# CVE-2026-72153: irqchip/crossbar: Use correct index in crossbar_domain_free()

> A Linux kernel bug in the crossbar IRQ chip driver causes incorrect index usage, potentially leading to out-of-bounds memory access and system instability.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72153, DEBIAN-CVE-2026-72153, GHSA-cjfc-rqm4-h9mg, UBUNTU-CVE-2026-72153

## What is CVE-2026-72153?

CVE-2026-72153 is a memory corruption 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/crossbar: Use correct index in crossbar_domain_free()

crossbar_domain_free() resets the domain data and then uses the nulled
out irq_data->hwirq member as index to reset the irq_map[] entry and to
write the relevant crossbar register with a safe entry. That means it
never frees the correct index and keeps the crossbar register connection
to the source interrupt active.

If it would not reset the domain data, then this would be even worse as
irq_data->hwirq holds the source interrupt number, but both the map and
register index need the corresponding GIC SPI number and not the source
interrupt number. This might even result in an out of bounds access as
the source interrupt number can be higher than the maximal index space.

Fix this by using the GIC SPI index from the parent domain's irq_data.

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


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

Apply the vendor's patch.

## Is CVE-2026-72153 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72153 is a memory corruption 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-72153 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-72153/ (Markdown: https://insights.sbomify.com/CVE-2026-72153/index.md)
```

## Sources

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

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