CVE-2026-99345

published 19 Nov 2026 · updated 21 Nov 2026

KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0

6.5MediumCVSS 6.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c0b29d523ef363d1d7ccfb3199f0126b22a61f66, Kernel 5dc500a354cc8e109df678076ae3488094649468, Kernel 81c460713ca62fa33ee1241fda1ddaf099facb32 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0 Reject KVM_SET_NESTED_STATE if the incoming L1 host state has what is effectively an impossible EFER combination of LMA=1 but LME=0, i.e. if the state says long mode is active but not enabled. Unlike VMX, SVM doesn't have an explicit consistent check for the illegal combination; presumably hardware simply ignores EFER.LMA if EFER.LME=0. Unfortunately, KVM doesn't ignore EFER.LMA in this case and consumes the illegal state when constructing the shadow MMU for L2. E.g. if userspace also clears CR4.PAE, then kvm_calc_cpu_role() will compute a role with 4 or 5 levels of paging, but shadow_mmu_init_context() will wire up the MMU to use the paging32 template, which maxes out its levels at 2. Note, the "real badness" is effectively the same as what happened with the nVMX bug fixed by commit 112e66017bff ("KVM: nVMX: add missing consistency checks for CR0 and CR4"). Unfortunately, the sanity check added by commit 72e2fb24a0b0 ("KVM: x86/mmu: Bug the VM if a vCPU ends up in long mode without PAE enabled") doesn't work for this case, since L2 state is active at the time of the page fault, but it's L1 that has the bad state.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <c0b29d523ef363d1d7ccfb3199f0126b22a61f66, >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <5dc500a354cc8e109df678076ae3488094649468, >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <81c460713ca62fa33ee1241fda1ddaf099facb32, >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <98362865bb626bb5e76cede98555d7cd4fefc016, =5.8c0b29d523ef363d1d7ccfb3199f0126b22a61f66, 5dc500a354cc8e109df678076ae3488094649468, 81c460713ca62fa33ee1241fda1ddaf099facb32, 98362865bb626bb5e76cede98555d7cd4fefc016
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.2, >=5.8.0 <6.12.1186.18.64, 7.3.2, 6.12.118

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99345 severity on Zeptric[![CVE-2026-99345](https://zeptric.io/badge/cve/CVE-2026-99345.svg)](https://zeptric.io/cve/CVE-2026-99345)