Skip to main content
VulnerabilityPublished

CVE-2026-99345: Linux kernel · KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99345

Not known to be exploited · fixed in c0b29d523ef363d1d7ccfb3199f0126b22a61f66 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in c0b29d523ef363d1d7ccfb3199f0126b22a61f66, 98362865bb626bb5e76cede98555d7cd4fefc016, 81c460713ca62fa33ee1241fda1ddaf099facb32 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to c0b29d523ef363d1d7ccfb3199f0126b22a61f66, 98362865bb626bb5e76cede98555d7cd4fefc016, 81c460713ca62fa33ee1241fda1ddaf099facb32 or 5dc500a354cc8e109df678076ae3488094649468.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < c0b29d523ef363d1d7ccfb3199f0126b22a61f66
Fixed in
  • c0b29d523ef363d1d7ccfb3199f0126b22a61f66
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 98362865bb626bb5e76cede98555d7cd4fefc016
Fixed in
  • 98362865bb626bb5e76cede98555d7cd4fefc016
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 81c460713ca62fa33ee1241fda1ddaf099facb32
Fixed in
  • 81c460713ca62fa33ee1241fda1ddaf099facb32
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 5dc500a354cc8e109df678076ae3488094649468
Fixed in
  • 5dc500a354cc8e109df678076ae3488094649468
LinuxLinuxAffected
  • =5.8
Fixed in–

Description

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.

References

Community reviews

Loading reviews…