ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ca9ae5ec4ef0ed13833b03297ab319676965492c · < 596e079c362ac17ed02aa1b99fdc444d62072a01| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure
When failing the driver probe because of invalid firmware properties, the GTDT driver unmaps the interrupt that it mapped earlier.
However, it never checks whether the mapping of the interrupt actially succeeded. Even more, should the firmware report an illegal interrupt number that overlaps with the GIC SGI range, this can result in an IPI being unmapped, and subsequent fireworks (as reported by Dann Frazier).
Rework the driver to have a slightly saner behaviour and actually check whether the interrupt has been mapped before unmapping things.
From the CVE record · Linux
The Linux kernel’s ACPI GTDT driver can unmap an interrupt it did not successfully map when a watchdog probe fails because of invalid firmware properties. If firmware supplies an illegal interrupt number overlapping the GIC SGI range, this can unmap an IPI. The input does not identify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the ACPI GTDT driver should check their exposure; affected versions are not specified.