Bug 2516741 (CVE-2026-72153) - CVE-2026-72153 kernel: irqchip/crossbar: Use correct index in crossbar_domain_free()
Summary: CVE-2026-72153 kernel: irqchip/crossbar: Use correct index in crossbar_domain...
Keywords:
Status: NEW
Alias: CVE-2026-72153
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 06:28 UTC by OSIDB Bzimport
Modified: 2026-08-18 13:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-15 06:28:39 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.