CVE-2026-45851: efi: Fix reservation of unaccepted memory table

Published May 27, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

efi: Fix reservation of unaccepted memory table

The reserveunaccepted() 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 acceptmemory().

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.

Affected Software

11 affected components
Linux Linux kernel
Linux Linux kernel>=6.6.1<6.6.128
Linux Linux kernel>=6.7<6.12.75
Linux Linux kernel>=6.13<6.18.14
Linux Linux kernel>=6.19<6.19.4
Linux Linux kernel=6.6
Linux Linux kernel=6.6-rc3
Linux Linux kernel=6.6-rc4
Linux Linux kernel=6.6-rc5
Linux Linux kernel=6.6-rc6
Linux Linux kernel=6.6-rc7

Event History

May 27, 2026
CVE Published
via MITRE·12:15 PM
Data Sourced
via MITRE·12:15 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which systems are most likely to encounter this issue?

The issue was observed when starting Intel TDX virtual machines with specific memory sizes, for example greater than 64 GB. It depends on an unaccepted memory table whose physical start address is not page-aligned and whose range crosses into a page not covered by the incorrect reservation.

2

What is the operational impact if the affected memory table is not fully reserved?

Part of the unaccepted memory table can be overwritten or become inaccessible. This can cause a kernel panic in accept_memory().

3

Does exploitation require remote access or user interaction?

The supplied CVSS vector identifies the attack vector as local, requires low privileges, and requires no user interaction. The description specifically describes a kernel memory-reservation error during the affected VM startup conditions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203