Skip to content
Breach Index · running record

AMD and CVE-2026-99312: a Linux KVM flaw on AMD hosts (not a breach)

AMD EPYC processors run a large share of cloud and private-cloud virtualisation hosts, so a hypervisor flaw that only bites on AMD matters to anyone renting or running virtual machines. This page tracks vulnerabilities that name AMD platforms and keeps them apart from any claim of a breach.

Short answer

Was AMD hacked?

No, CVE-2026-99312 is not a breach of AMD, and it is not a flaw in AMD hardware or firmware. It is a vulnerability in KVM, the hypervisor in the Linux kernel, in the code for AMD's virtualisation extension (SVM). The CVE record, published by the Linux kernel CNA on 18 November 2026, says it "only affects nested SVM"; Intel hosts are not affected.

Terra Security showed a guest on an AMD KVM host with nested virtualisation enabled reading about 127 GB of host memory on a DigitalOcean Droplet. Fixed Linux kernels are 6.12.118, 6.18.64, 7.3.5 and 7.4-rc2; the mitigation is to set kvm_amd nested=0. DigitalOcean says it live-patched its fleet. No exploitation is reported, and it is not in CISA KEV.

Timeline at a glance

  1. 21 Oct 2026Terra Security reports the KVM nested-SVM flaw to the Linux KVM maintainers. (Terra Security)Not a breach
  2. 17 Nov 2026Fixed in Linux stable 7.3.5, 6.18.64 and 6.12.118. (CVE record)Not a breach
  3. 18 Nov 2026CVE-2026-99312 published (CVSS 8.8); affects AMD KVM hosts with nested virtualisation only. (CVE record)Not a breach
  4. 19 Nov 2026DigitalOcean says it live-patched its AMD hypervisors; no customer action needed. (DigitalOcean)Confirmed

Last updated 21 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

AMD incident timeline, in detail

Confirmed = acknowledged by AMD, a regulator filing or a court. Reported = credible reporting AMD has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Nov 2026Not a breachHypervisor vulnerability (Linux KVM, AMD SVM code path)

CVE-2026-99312: guest-to-host memory access on AMD KVM hosts with nested virtualisation

What happened. KVM did not reset the MMU context when emulating an INIT while a nested guest ran with paging off, leaving a stale pointer to a freed page-table page. Only nested SVM is affected. Fixed in Linux 6.12.118, 6.18.64, 7.3.5 and 7.4-rc2.

Impact. Terra Security read about 127 GB of host RAM from a DigitalOcean Droplet and, on its own server, wrote chosen bytes into a host kernel page. Red Hat says AMD hosts without nested virtualisation and all Intel hosts are not affected. No exploitation reported.

Sources: CVE record · Terra Security · DigitalOcean · Red Hat

Where the reports disagree

  • Severity: the Linux kernel CNA scores it CVSS 3.1 8.8; Red Hat's preliminary score is 7.8 (high attack complexity). NVD had not scored it on 21 November 2026.
  • Vendor: the CVE is assigned to the Linux kernel, not AMD, and AMD's product security page lists no bulletin for it. It appears here because the flaw is reachable only on AMD virtualisation hosts.

The pattern across the record

Nested virtualisation widens the hypervisor surface

The flaw is only reachable when kvm_amd allows nested guests. Terra says many providers it surveyed were not exposed because they leave nesting off on AMD.

Vulnerabilities are not breaches

Nothing reported shows an intrusion at AMD. The exposure is to operators of AMD KVM hosts that run untrusted guests with nesting enabled.

What it means for AMD customers — and what to do

If you run or rent virtual machines on AMD hosts, the question is whether the host allows nested virtualisation and runs a fixed kernel.

  1. 1.Check nesting on AMD hosts

    cat /sys/module/kvm_amd/parameters/nested; set kvm_amd nested=0 where nobody needs it, persisted in /etc/modprobe.d.

    Fixed kernels and steps
  2. 2.Patch the host kernel

    Move to 6.12.118, 6.18.64, 7.3.5 or later, or your distribution's fixed kernel.

  3. 3.Ask your cloud provider

    Patching a guest does not change host exposure. Ask whether nesting is on and when the host was patched.

  4. 4.Harden the hypervisor baseline

    Make nesting an approved exception.

    KVM Hardening Checklist
Take this with you
Incident timeline · What AMD customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 21 November 2026.

  1. 1.CVE-2026-99312 (CNA: Linux) — CVE.org, 18 Nov 2026
  2. 2.KVM guest-to-host escape — Terra Security, 18 Nov 2026
  3. 3.Virtualization, Responsible Disclosure, and CVE-2026-99312 — DigitalOcean, 19 Nov 2026
  4. 4.CVE-2026-99312 — Red Hat, 20 Nov 2026
  5. 5.AMD product security (checked: no bulletin for this CVE) — AMD, 21 Nov 2026

Frequently asked questions

Was AMD hacked?

No. CVE-2026-99312 is a vulnerability in Linux KVM code for AMD virtualisation, not a breach of AMD and not a flaw in AMD chips.

Are Intel hosts affected by CVE-2026-99312?

No. The fix commit says only nested SVM (AMD) is affected, because Intel VMX always intercepts INIT.

How do I mitigate CVE-2026-99312?

Update the host kernel to 6.12.118, 6.18.64, 7.3.5 or later, or set kvm_amd nested=0 to turn off nested virtualisation.

Our coverage of AMD

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by AMD. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.