CVE-2026-72153

irqchip/crossbar: Use correct index in crossbar_domain_free()

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1 ≤ v < 5.10.2614.1 ≤ v < 5.15.2124.1 ≤ v < 6.1.1784.1 ≤ v < 6.12.974.1 ≤ v < 6.18.404.1 ≤ v < 6.6.1454.1 ≤ v < 7.1.54.1 ≤ v < 7.24.1783d31863fb826f1a3754a2d5959a022a1b12d54
Vendor states this is fixed in 043db005a8d6932dc7d217c86307e9af0bc10ddc (fixed)
Vendor states this is fixed in 13bdb5140405ff283f9052e65ee1d5c2303765c7 (fixed)
Vendor states this is fixed in 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df (fixed)
Vendor states this is fixed in 36ca587f55a2c04468a89fd16174bb2f78dc04ec (fixed)
Vendor states this is fixed in 424130169dc03b84ea604685409726d61bcec859 (fixed)
Vendor states this is fixed in cca649a23a5fc8aae536fc27a0546c67690a4078 (fixed)
Vendor states this is fixed in ccc3664679763d2d6f067c28729bdff627bb72d0 (fixed)
Vendor states this is fixed in e5be5d452d5f1efbb3342da2b00029be6c99034e (fixed)
Vendor states this is fixed in 4.1 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card