Answer in brief
CVE-2026-72153 records a Unknown severity vulnerability in irqchip/crossbar: Use correct index in crossbar_domain_free(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72153 records a Unknown severity vulnerability in irqchip/crossbar: Use correct index in crossbar_domain_free(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=783d31863fb826f1a3754a2d5959a022a1b12d54 <13bdb5140405ff283f9052e65ee1d5c2303765c7 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <ccc3664679763d2d6f067c28729bdff627bb72d0 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <424130169dc03b84ea604685409726d61bcec859 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <cca649a23a5fc8aae536fc27a0546c67690a4078 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <36ca587f55a2c04468a89fd16174bb2f78dc04ec || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <e5be5d452d5f1efbb3342da2b00029be6c99034e || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <043db005a8d6932dc7d217c86307e9af0bc10ddc | 13bdb5140405ff283f9052e65ee1d5c2303765c7, 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df, ccc3664679763d2d6f067c28729bdff627bb72d0, 424130169dc03b84ea604685409726d61bcec859, cca649a23a5fc8aae536fc27a0546c67690a4078, 36ca587f55a2c04468a89fd16174bb2f78dc04ec, e5be5d452d5f1efbb3342da2b00029be6c99034e, 043db005a8d6932dc7d217c86307e9af0bc10ddc |
| Linux/Linuxgeneric | 4.1 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=783d31863fb826f1a3754a2d5959a022a1b12d54 <13bdb5140405ff283f9052e65ee1d5c2303765c7 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <ccc3664679763d2d6f067c28729bdff627bb72d0 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <424130169dc03b84ea604685409726d61bcec859 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <cca649a23a5fc8aae536fc27a0546c67690a4078 || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <36ca587f55a2c04468a89fd16174bb2f78dc04ec || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <e5be5d452d5f1efbb3342da2b00029be6c99034e || >=783d31863fb826f1a3754a2d5959a022a1b12d54 <043db005a8d6932dc7d217c86307e9af0bc10ddc | 13bdb5140405ff283f9052e65ee1d5c2303765c7, 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df, ccc3664679763d2d6f067c28729bdff627bb72d0, 424130169dc03b84ea604685409726d61bcec859, cca649a23a5fc8aae536fc27a0546c67690a4078, 36ca587f55a2c04468a89fd16174bb2f78dc04ec, e5be5d452d5f1efbb3342da2b00029be6c99034e, 043db005a8d6932dc7d217c86307e9af0bc10ddc |
| Linux/Linuxgeneric | 4.1 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.