Linux KVM flaw CVE-2026-99312 affects AMD hosts with nested virtualization
CVE-2026-99312 is a Linux KVM flaw that affects only AMD hosts with nested virtualization enabled; fixes shipped in kernels 7.3.5, 6.18.64, and 6.12.118.
According to The Hacker News, CVE-2026-99312 is a Linux kernel KVM (Kernel-based Virtual Machine) vulnerability that affects only hosts with AMD processors and nested virtualization enabled. The CVE was published on November 18, 2026, and the Linux kernel’s CVE team scores it 8.8 out of 10.
The flaw is in the Linux kernel file arch/x86/kvm/x86.c. The bug only affects nested SVM (AMD’s virtualization support), as INIT is an unconditional intercept on VMX (Intel’s virtualization support). The report says Intel-based KVM hosts are not affected because the vulnerable code exists only in KVM’s support for nested virtualization on AMD.
The report says the affected code entered the 6.1 kernel in 2022 and was carried into the 5.15.81 and 6.0.11 releases, so older kernel lines and distribution kernels built on them are in range. The report adds that the Linux KVM maintainers were told on October 21 and merged a fix on November 2.
The report says researchers read about 127 GB of a cloud server’s memory from inside a virtual machine of their own on DigitalOcean. It says there are no reports of the flaw being used outside research, according to VirtFusion, and no exploit code has been published; it also says no guidance exists for detecting a past attempt.
The report says Debian’s security tracker lists the kernels in all of its releases as vulnerable, with a fix only in unstable, and Ubuntu’s CVE tracker rates the flaw High and lists its kernels as vulnerable with no fixed package released. It says Red Hat lists the Enterprise Linux 9 and 10 kernels as affected with the fix deferred, and the Enterprise Linux 8 kernel as not affected.
What to do
The report says upstream the fix shipped in stable kernel 7.3.5 and in the long-term kernels 6.18.64 and 6.12.118. The fix lives in the host kernel; updating the operating systems inside the VMs changes nothing, and a host keeps running its old kernel until it is rebooted. Until a fixed host kernel is installed and the host rebooted, the only available protection is to turn nested virtualization off. The report says nested virtualization is on by default in the kernel’s kvm_amd module, according to VirtFusion’s operator guide, so an unpatched host is exposed unless the setting was deliberately changed.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .