efi: Fix reservation of unaccepted memory table
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
efi: Fix reservation of unaccepted memory table
The reserve_unaccepted() function incorrectly calculates the size of the memblock reservation for the unaccepted memory table. It aligns the size of the table, but fails to account for cases where the table's starting physical address (efi.unaccepted) is not page-aligned.
If the table starts at an offset within a page and its end crosses into a subsequent page that the aligned size does not cover, the end of the table will not be reserved. This can lead to the table being overwritten or inaccessible, causing a kernel panic in accept_memory().
This issue was observed when starting Intel TDX VMs with specific memory sizes (e.g., > 64GB).
Fix this by calculating the end address first (including the unaligned start) and then aligning it up, ensuring the entire range is covered by the reservation.
From the CVE record · Linux
The Linux kernel may fail to reserve the full EFI unaccepted memory table when the table starts at an unaligned address. The table can then be overwritten or become inaccessible, causing a kernel panic in accept_memory(). This was observed when starting Intel TDX VMs with specific memory sizes; the input does not establish an attacker route, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels in Intel TDX VMs should check their deployments; affected versions are not specified.