Linux KVM Vulnerability CVE-2026-99312: AMD Hosts With Nested Virtualization Affected, What Is Confirmed and How to Check Yours
A Linux kernel flaw in the KVM hypervisor, CVE-2026-99312, affects hosts with AMD processors and nested virtualization enabled. Here is what is confirmed, what is not known, and the one command that tells you if a host is in scope.
Where Worldwide
On this page 9 sections
A newly published flaw in the Linux kernel's KVM hypervisor, tracked as CVE-2026-99312, affects servers with AMD processors that have nested virtualization turned on. If your business runs virtual machines on its own AMD-based Linux servers, or rents them from a host that does, this week you should check one setting and schedule a kernel update.
The CVE record is dated November 18, 2026. The kernel already has a fix, and The Hacker News reports no attacks so far. Below is what is confirmed, what is not, and how to check your own hosts.
What is CVE-2026-99312?
CVE-2026-99312 is a vulnerability in the Linux kernel. The official CVE record opens with the standard kernel wording, "In the Linux kernel, the following vulnerability has been resolved:". The kernel team uses that line for flaws that already have a fix.
The Debian security tracker describes the fix in one line: "Force an MMU reset when emulating an INIT even if paging was already disabled". In plain terms, KVM (the Kernel-based Virtual Machine, the hypervisor built into Linux) sometimes has to emulate an INIT, a reset signal for a virtual processor. When it does, it now always resets its memory translation state, even in a case where it used to skip that step. The MMU is the part of the system that maps memory, and a hypervisor depends on it to keep virtual machines apart.
How serious is the KVM flaw?
The CVE record scores the flaw with this CVSS 3.1 vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Here is what each part means:
| Part | What it means |
|---|---|
| AV:L | The attacker needs local access. It is not a network-only attack |
| AC:L | The attack is not complex |
| PR:L | Only low privileges are needed |
| UI:N | Nobody has to click or approve anything |
| S:C | Scope changed: the impact can reach beyond the vulnerable component |
| C:H, I:H, A:H | High impact on confidentiality, integrity and availability |
The parts that matter most for a hypervisor are the scope change and the high ratings for confidentiality, integrity and availability. The information we confirmed does not include a numeric base score, so we are not giving one.
Is my server affected? AMD vs Intel KVM hosts
The Hacker News reports that the flaw affects "Only hosts with AMD processors and nested virtualization enabled". By that report, KVM hosts with Intel processors are not affected. Nested virtualization lets a virtual machine run its own virtual machines inside it, for example to run a hypervisor inside a VM.
On versions: the CVE record's version data lists Linux kernel 6.12.118. That entry alone does not tell us whether 6.12.118 marks where the bug starts or where it is fixed, so do not treat it as a target version. We have not confirmed which kernel package fixes the flaw for each distribution. Check your distribution's own security tracker.
How to check if nested virtualization is enabled on AMD
Run this on each Linux host that runs KVM:
cat /sys/module/kvm_amd/parameters/nested
If the output says nested virtualization is enabled, treat that host as in scope until it runs a patched kernel. If the file does not exist, the kvm_amd module is not loaded on that machine, so it is not currently acting as an AMD KVM host.
What to do this week
| Step | What to do |
|---|---|
| 1. Inventory | List every Linux server that runs virtual machines with KVM, and note which have AMD processors |
| 2. Check the setting | On each AMD host, run cat /sys/module/kvm_amd/parameters/nested and record the result |
| 3. Patch | Install your distribution's kernel update that includes the fix for CVE-2026-99312. The Debian security tracker and your distribution's own tracker list the packages |
| 4. Reboot | A new kernel only protects the host once the host is running it. Plan a maintenance window for the VMs on it |
| 5. Review nested use | If no one needs nested virtualization on a host, ask your vendor or administrator whether turning it off is a sensible interim step. The report names hosts with it enabled as the affected group |
| 6. Ask your provider | If you rent virtual or cloud servers, you cannot check the host yourself. Ask your provider whether its AMD KVM hosts are patched for CVE-2026-99312 |
Step 4 is the one teams skip most often. We covered that gap in Updated Is Not the Same as Patched.
What is not known yet
- Attacks: The Hacker News reports that "There are no reports of the flaw being used outside research". That does not mean no one is trying, only that nobody has reported it.
- Real-world impact: The sources we confirmed do not spell out exactly what an attacker could read or change in practice. Some coverage goes into more detail. We could not check those details against a primary source, so we are not repeating them.
- Fixed versions: We have not confirmed a full list of fixed kernel versions by distribution.
- Cloud providers: We have not confirmed which hosting or cloud providers run affected configurations, or whether they have patched.
The Hacker News report cites Oren Yomtov, a researcher at the security firm Terra Security. None of our sources include a public write-up from the researchers.
Why this matters for a business network
Many businesses run several servers as virtual machines on one physical machine: the website, a database, a file server, an internal tool. That setup is safe only if each virtual machine stays walled off from the others and from the host. A hypervisor flaw rated as a scope change goes after that wall.
In practice the danger is a chain of problems. A website VM gets compromised through something ordinary, like an outdated plugin (see why WordPress sites get hacked). After that, the host's isolation is what stops the attacker from reaching everything else on the same machine. If you host virtual machines for other people, such as an agency hosting client sites, the stakes are higher, because the other tenants are not yours to trust.
For businesses that self-host, someone has to own kernel updates and reboots on the host, not just inside each VM. If no one has clearly been given that job, read Who Is Patching the Software That Runs Your Business?. Our page on self-hosting infrastructure explains how we approach it.
Linux KVM vulnerability questions people are asking
What is CVE-2026-99312?
It is a vulnerability in the Linux kernel's KVM hypervisor. The fix makes KVM fully reset its memory translation state when it emulates a virtual CPU INIT.
Are Intel KVM hosts affected?
According to The Hacker News, no. It reports that only hosts with AMD processors and nested virtualization enabled are affected.
How do I check if nested virtualization is enabled?
On an AMD Linux host, run cat /sys/module/kvm_amd/parameters/nested. The output shows whether nested virtualization is on.
Is CVE-2026-99312 being exploited?
The Hacker News reports no use of the flaw outside research. No source we confirmed reports attacks.
Is there a fix for the KVM flaw?
Yes. The kernel has a fix, described by Debian as "Force an MMU reset when emulating an INIT even if paging was already disabled". Install your distribution's updated kernel and reboot.
What kernel version fixes CVE-2026-99312?
We have not confirmed a fixed version per distribution. The CVE record lists 6.12.118 in its version data. Check your distribution's security tracker for the exact package.
Does this affect my cloud server?
It depends on your provider's hosts, which you cannot inspect. Ask whether its AMD KVM hosts with nested virtualization are patched.
The bigger lesson
This flaw only matters where someone turned on a specific feature, nested virtualization, on a specific kind of hardware. Most businesses could not say which of their hosts have that switch on. A short record of each server's processor, kernel version and settings turns a week of guessing into a five-minute check. Knowing your own setup is what makes advisories like this one quick to act on.
For help hardening and patching your servers, see security hardening or request a quote.
Get security alerts by email, with the free checklist, at our security alerts page.
Sources: CVE Program record for CVE-2026-99312; Debian security tracker: CVE-2026-99312; The Hacker News.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
PHP Critical Vulnerability: Seven RCE Flaws Fixed in PHP 8.5.13 and 8.6.0, Which Version to Install for Your Branch and Who Is Exposed
PHP's 19 November 2026 security releases fix seven critical remote code execution flaws. Here is which version...
PHP Session Vulnerability: CVE-2026-126714 and CVE-2026-115560 Can Lead to Remote Code Execution, Fixed in PHP 8.5.13, and What to Check This Week
PHP has fixed two session flaws, CVE-2026-126714 and CVE-2026-115560, that can lead to remote code execution....
F5 BIG-IP Vulnerability: Critical No-Login Flaws in APM and iRules Can Crash TMM, No Workaround, and the Emergency Hotfixes to Install
F5 shipped emergency hotfixes for critical BIG-IP APM and iRules flaws that let attackers with no login crash...