Threats Tagged 'cve-2026-45851'
View all threats tagged with 'cve-2026-45851'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-45851'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel's EFI memory reservation logic causes incorrect reservation of the unaccepted memory table. The reserve_unaccepted() function miscalculates the reservation size when the table's starting physical address is not page-aligned, potentially leaving part of the table unreserved. This can lead to kernel panic during memory acceptance, notably observed on Intel TDX VMs with large memory sizes. Join the discussion | GCVE Database | 05/27/2026, 15:33:13 UTC Added: 06/26/2026, 22:06:40 UTC |
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. Join the discussion | GCVE Database | 05/27/2026, 14:16:00 UTC Added: 07/18/2026, 11:19:28 UTC |
Showing 1 to 2 of 2 results