What Happened
Linux KVM CVE-2026-99312 breaks the wall between guest virtual machines and the host on AMD servers with nested virtualization enabled, The Hacker News reports. Oren Yomtov of Terra Security found the bug and reported it through DigitalOcean’s bug bounty. In testing, he read about 127 GB of host RAM from inside a DigitalOcean Droplet. On his own bare-metal AMD server, he wrote 32 bytes into host kernel memory.
The root cause is a dangling pointer after an INIT on a nested VM. The 2022 fix for CVE-2022-3344 introduced it, and it sat in the kernel for almost four years. Intel hosts are not affected. Fixes landed upstream in kernel 7.3.5 and LTS releases 6.18.64 and 6.12.118. Debian has no fix outside unstable, Ubuntu rates it High with no fixed package, and RHEL 9 and 10 are affected with the fix deferred. The Linux kernel CNA scores it 8.8. Red Hat rates it 5.6. DigitalOcean live-patched its fleet, and no exploitation outside research is reported.
Why This Matters for Canadian Organizations
Canadian hosting providers, managed service providers, universities, and enterprise private clouds run KVM on AMD EPYC servers. Nested virtualization is on by default in kvm_amd. Many teams never turn it off. A tenant reading host memory reaches other tenants’ keys, tokens, and personal data. For a Canadian host, a cross-tenant leak triggers PIPEDA breach reporting and Quebec Law 25 duties for every affected client. Banks and insurers relying on KVM-based platforms must also weigh OSFI B-13 technology risk expectations.
The gap between the upstream fix and distribution packages is the real risk. Your patch management tools will show nothing to install for most distributions today.
What to Do
Check every AMD KVM host with cat /sys/module/kvm_amd/parameters/nested. If you do not need nested virtualization, set options kvm_amd nested=0 and reboot the host. Updating guest operating systems does not help. Track your distribution’s advisory and apply the kernel update when it ships. Prioritize multi-tenant hosts and hosts running untrusted workloads. Ask your cloud and hosting providers whether they run AMD nested virtualization and how they mitigated this flaw. Follow our TechTalk coverage and today’s Daily Brief for updates.






