Security alert · High
Linux KVM flaw CVE-2026-99312 lets guest VMs access host memory on AMD hosts
· 4 minutes read · Centoculus Security Team
Known since
Affected: Linux kernel KVM (kvm_amd, nested SVM) on AMD hosts. The flaw entered in 6.1, 5.15.81 and 6.0.11 and is fixed in 7.3.5, 6.18.64 and 6.12.118
What happened
On 18 November 2026 the Linux kernel team published CVE-2026-99312, a flaw in KVM, the hypervisor built into the Linux kernel. The kernel's CVE team scores it 8.8 out of 10. Red Hat's preliminary assessment rates it Moderate (5.6) and treats it as denial of service only.
The bug is in KVM's support for nested virtualization on AMD processors (nested SVM). When a nested VM is stopped by an INIT signal, KVM does not reset the outer VM's memory-management state. A pointer is left pointing at a page the kernel has already freed. Terra Security researcher Oren Yomtov found the flaw. According to the researchers, a guest can place forged page-table entries in that freed page once the kernel reuses it, and so reach physical memory on the host. On a DigitalOcean Droplet they read about 127 GB of host RAM. On their own AMD server they also wrote data into the host kernel's memory. On a shared host, that memory can include other customers' VMs.
The attacker needs root access inside a guest VM on a vulnerable host. Network access to the host is not enough. The fix makes KVM reset its memory-management state on every INIT. The bug came in with a 2022 fix for CVE-2022-3344.
CVE-2026-99312 is not in CISA's catalogue of known exploited vulnerabilities. VirtFusion says there are no reports of the flaw being used outside research. No exploit code has been published.
Who is affected
Only KVM hosts with AMD processors and nested virtualization enabled are affected. This includes hosts managed through platforms that use KVM. The kvm_amd module enables nested virtualization by default, so an unpatched AMD host is exposed unless someone turned it off.
The following are not affected:
- Intel-based KVM hosts. On Intel, INIT is always intercepted, so the vulnerable code path cannot be reached.
- AMD hosts with nested virtualization turned off.
- Servers that do not run KVM guests. This covers ordinary web and mail servers, and VMs or VPS where you are only the guest.
- Red Hat Enterprise Linux 8. Red Hat lists its kernel as not affected.
Updating the operating system inside your VMs does nothing for this flaw. The fix belongs in the host kernel. If you rent VPS or cloud servers, it is your provider's job. DigitalOcean has patched its own hosts and says customers do not need to do anything.
Affected versions: the bug entered the 6.1 kernel in 2022 and was also carried into 5.15.81 and 6.0.11. Older kernel lines from those versions on, and distribution kernels built on them, are in range. Upstream fixes are in 7.3.5, 6.18.64 and 6.12.118.
Distribution status at the time of the source report:
- Debian: kernels in all releases listed as vulnerable. The fix is only in unstable.
- Ubuntu: rated High, kernels listed as vulnerable, no fixed package yet.
- RHEL 9 and 10: listed as affected, fix deferred.
What to do now
- On every AMD KVM host, check whether nested virtualization is on:
cat /sys/module/kvm_amd/parameters/nested. A value of1orYmeans it is on and the host is exposed. - If your distribution has a fixed host kernel, install it with your package manager. Otherwise use an upstream kernel 7.3.5, 6.18.64 or 6.12.118 or later. Check your distribution's security tracker for the fixed package version.
- Reboot the host. The old kernel keeps running until you do. Plan for the guest downtime or migrate VMs first.
- If no fixed kernel is available yet, turn nested virtualization off. Add
options kvm_amd nested=0to a file under/etc/modprobe.d/, for example/etc/modprobe.d/kvm-amd.conf, then reboot the host. The setting cannot be changed while VMs are running. After this change, guests can no longer run VMs of their own, so warn customers who rely on that first. - Once a fixed kernel is out for your distribution, install it and reboot. Only then turn nested virtualization back on if you need it.
How to check whether you are affected
- Check the CPU with
lscpu | grep -i 'vendor id'. OnlyAuthenticAMDhosts are relevant. - Check that the AMD KVM module is loaded with
lsmod | grep kvm_amd. If it is not loaded, the host does not run KVM guests on AMD and is not affected. - Check the nested setting as in step 1.
- After rebooting, confirm the running kernel with
uname -r. Compare it with the fixed versions above or with your distribution's advisory. Read the nested setting again if you changed it.
VirtFusion says there is no guidance for detecting a past exploitation attempt.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-99312
- https://git.kernel.org/stable/c/24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
More sources (4)
More on Linux kernel
If you run Linux servers, also check
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.