Vulnerability · Published Jun 24, 2026 · Assigned by Linux

CVE-2026-52959virt: sev-guest: Do not use host-controlled page order in cleanup path

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.1%top 98.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Do not use host-controlled page order in cleanup path When issuing an extended guest request (SVM_VMGEXIT_EXT_GUEST_REQUEST), get_ext_report() allocates a buffer to retrieve a certificate blob from the host, keeping track of its size in report_req->certs_len. However, the host may return SNP_GUEST_VMM_ERR_INVALID_LEN, indicating an invalid buffer size, as well as the expected length of such buffer. get_ext_report() subsequently updates report_req->certs_len with the host-controlled value, and cleans up the buffer by computing a page order from such value. This is incorrect, as the host-provided length may not match the page order of the original allocation, potentially resulting in corruption in the page allocator. Fix this by using alloc_pages_exact() instead, and reusing @npages to compute the size passed to free_pages_exact(). For consistency, also use @npages to compute the size when allocating the pages, even though this last change has no functional effect.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.0.10-1DEBIAN-CVE-2026-52959
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-52959
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-52959
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-52959
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-52959
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-52959
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-52959
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-52959

Affected products (as reported)

VendorProductVersions
Linux Linux 3e385c0d6ce88ac9916dcf84267bd5855d830748 – before 3f6fb0211b39aaa1b841260681dd02ca6b693ed53e385c0d6ce88ac9916dcf84267bd5855d830748 – before 9e48b4f813d2c3db75d522aa82ab705ce04b7e2d3e385c0d6ce88ac9916dcf84267bd5855d830748 – before 23e6a1ca04ae44806439a5a446e62e4d42e80bb40b16521f95c875e79d657cb8d6911c15080dbb806.13.8 – before 6.14
Linux Linux 6.14

References