arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0be7320a635c2e434e8b67e0e9474a85ceb421c4 · < bc7fbb37e3d2df59336eadbd6a56be632e3c7df7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry
In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map back to the cpu and use that to index into a cpumask. As such, a valid ID is needed.
If an MPIDR check fails in acpi_map_gic_cpu_interface() it is possible for the entry in cpu_madt_gicc[cpu] == NULL. This function would then cause a NULL pointer dereference. Whilst a path to trigger this has not been established, harden this caller against the possibility.
From the CVE record · Linux
The arm64 ACPI CPU lookup in the Linux kernel could dereference a NULL pointer if an MPIDR check fails and leaves a CPU entry missing. No trigger path has been established, so whether an attacker can exploit this—and what access or interaction that would require—is unknown.
Engineers running the Linux kernel on arm64 systems with ACPI should check whether their kernel includes the fix; affected versions were not specified.