irqchip/crossbar: Use correct index in crossbar_domain_free()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.1
References 8
git.kernel.org
- stable/c/13bdb5140405ff283f9052e65ee1d5c2303765c7
- stable/c/1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df
- stable/c/ccc3664679763d2d6f067c28729bdff627bb72d0
- stable/c/424130169dc03b84ea604685409726d61bcec859
- stable/c/cca649a23a5fc8aae536fc27a0546c67690a4078
- stable/c/36ca587f55a2c04468a89fd16174bb2f78dc04ec
- stable/c/e5be5d452d5f1efbb3342da2b00029be6c99034e
- stable/c/043db005a8d6932dc7d217c86307e9af0bc10ddc