العربية
🚨 BreakingSonicWall Gen 6 Firewalls Reach End of Security Patches

Linux KVM CVE-2026-99312 Lets AMD Guest VMs Read Host Memory

فريق السايبر العربياقرأ بالعربية

A use-after-free in Linux KVM nested virtualization on AMD hosts let a guest VM read about 127 GB of host RAM. Fixed in kernels 7.3.5, 6.18.64 and 6.12.118.

Source image for: Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts
Image: The Hacker News

⚡ Why it matters

On shared cloud hosts, host memory can hold other tenants' VMs, so the bug undermines the isolation that virtualised hosting depends on.

Terra Security researcher Oren Yomtov disclosed CVE-2026-99312, a bug in the Linux kernel's built-in KVM hypervisor. Only hosts with AMD processors and nested virtualization enabled are affected; Intel hosts are not.

Impact

From inside their own VM on DigitalOcean, the researchers read around 127 GB of host memory. On their own bare-metal AMD server they also wrote data into live host kernel memory. An attacker needs root inside a guest on a vulnerable host; network access alone is not enough.

Root cause

When an INIT signal stops a nested VM, KVM fails to restore the outer VM's nested page table pointer, leaving it pointing at freed memory. Once that page is reused, the guest can fill it with entries that map arbitrary host physical pages. The bug was introduced in 2022 by the fix for CVE-2022-3344.

Severity and status

The kernel CVE team rates it 8.8, while Red Hat's preliminary score is 5.6 (Moderate). There are no reports of in-the-wild exploitation and no public exploit code.

Fixed versions

The fix is in stable kernel 7.3.5 and long-term kernels 6.18.64 and 6.12.118. Affected code dates back to the 6.1 line and was backported to 5.15.81 and 6.0.11. At publication, Debian and Ubuntu had not shipped fixed packages for most releases; Red Hat lists RHEL 9 and 10 as affected and RHEL 8 as not affected.

Recommendations

  • Update the host kernel and reboot; patching guest operating systems does not help.
  • If you cannot patch yet, set options kvm_amd nested=0 and reboot the host.
  • Check the current state in /sys/module/kvm_amd/parameters/nested.
  • Warn tenants that rely on nested VMs before disabling the feature.

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories