CVE-2026-72153irqchip/crossbar: Use correct index in crossbar_domain_free()
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < 13bdb5140405ff283f9052e65ee1d5c2303765c7
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < ccc3664679763d2d6f067c28729bdff627bb72d0
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < 424130169dc03b84ea604685409726d61bcec859
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < cca649a23a5fc8aae536fc27a0546c67690a4078
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < 36ca587f55a2c04468a89fd16174bb2f78dc04ec
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < e5be5d452d5f1efbb3342da2b00029be6c99034e
- affected 783d31863fb826f1a3754a2d5959a022a1b12d54 – < 043db005a8d6932dc7d217c86307e9af0bc10ddc
- affected 4.1
- unaffected < 4.1
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/13bdb5140405ff283f9052e65ee1d5c2303765c7 (opens in a new tab)
- https://git.kernel.org/stable/c/1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df (opens in a new tab)
- https://git.kernel.org/stable/c/ccc3664679763d2d6f067c28729bdff627bb72d0 (opens in a new tab)
- https://git.kernel.org/stable/c/424130169dc03b84ea604685409726d61bcec859 (opens in a new tab)
- https://git.kernel.org/stable/c/cca649a23a5fc8aae536fc27a0546c67690a4078 (opens in a new tab)
- https://git.kernel.org/stable/c/36ca587f55a2c04468a89fd16174bb2f78dc04ec (opens in a new tab)
- https://git.kernel.org/stable/c/e5be5d452d5f1efbb3342da2b00029be6c99034e (opens in a new tab)
- https://git.kernel.org/stable/c/043db005a8d6932dc7d217c86307e9af0bc10ddc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-58911 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72153)Record last updated .