ACPI: processor: validate MADT IOAPIC entry bounds
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ecf5636dcd59cd5508641f995cc4c2bafedbb995 · < 4d8ecaa332c163f2b44aa5027bf061950b71b5f3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: processor: validate MADT IOAPIC entry bounds
The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after only locating a generic header. The _MAT path likewise passed a generic header to the IOAPIC helper.
Validate that a current record has a complete generic header, that its declared length is contained in the available record range, and that a typed IOAPIC record contains the full fixed IOAPIC body before reading its fields. Use the same relation for both MADT and _MAT provider paths.
From the CVE record · Linux
The Linux kernel’s ACPI processor IOAPIC hotplug lookup could read an IOAPIC record without confirming that its full body fits within the available MADT or _MAT record range. The input does not establish how an attacker could trigger this or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with ACPI processor IOAPIC hotplug support should check their kernel builds; affected versions are not specified.