irqchip/gic-v5: Check get_logical_index() return value in MADT IAFFID parsing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v5: Check get_logical_index() return value in MADT IAFFID parsing
In gic_acpi_parse_iaffid() a given MADT GICC entry might not correspond to a logical cpu recognized by the kernel, resulting in the cpu variable initialization to an error value.
Currently, the get_logical_index() return value is not checked for failure, which might result in out-of-bounds memory corruption while trying to index a per_cpu variable array.
Add a check to evaluate get_logical_index() return value.
From the CVE record · Linux
The Linux kernel does not check whether a MADT GICC entry maps to a recognized logical CPU during GIC-v5 parsing. If it does not, the kernel may use an error value to index a per-CPU array, causing out-of-bounds memory corruption. The input does not specify an attack path or whether authentication or user interaction is required.
Engineers running Linux kernels with GIC-v5 MADT parsing should check their versions; affected versions are not specified.