efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 33b6d03469b2206fb51ecc37f40411a857ad8fff · < 2e6871a632a99d9b9e2ce3a7847acabe99e5a26e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption
The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.
The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.
Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let's use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.
From the CVE record · Linux
The EFI stub can leave the TPM event log memory unreserved, allowing it to be corrupted after kexec. Parsing a corrupted log could crash the kernel. The input does not establish an attacker path, authentication requirements, or user-interaction requirements.
Operators running Linux kernels that use the EFI stub, TPM event logs, and kexec should check their kernel vendor's advisory for affected versions.