CVE-2026-99345
Severity unknownNo known exploitationFix availableKVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 10% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from cc440cdad5b7a4c1de12dace725209eb3e0cf663 before 98362865bb626bb5e76cede98555d7cd4fefc016 | 98362865bb626bb5e76cede98555d7cd4fefc016 | CVE Program |
| Linux | Linux | from cc440cdad5b7a4c1de12dace725209eb3e0cf663 before 81c460713ca62fa33ee1241fda1ddaf099facb32 | 81c460713ca62fa33ee1241fda1ddaf099facb32 | CVE Program |
| Linux | Linux | from cc440cdad5b7a4c1de12dace725209eb3e0cf663 before 5dc500a354cc8e109df678076ae3488094649468 | 5dc500a354cc8e109df678076ae3488094649468 | CVE Program |
| Linux | Linux | from cc440cdad5b7a4c1de12dace725209eb3e0cf663 before c0b29d523ef363d1d7ccfb3199f0126b22a61f66 | c0b29d523ef363d1d7ccfb3199f0126b22a61f66 | CVE Program |
| Linux | Linux | 5.8 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.8 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/5dc500a354cc8e109df678076ae3488094649468 (opens in a new tab)
- https://git.kernel.org/stable/c/81c460713ca62fa33ee1241fda1ddaf099facb32 (opens in a new tab)
- https://git.kernel.org/stable/c/98362865bb626bb5e76cede98555d7cd4fefc016 (opens in a new tab)
- https://git.kernel.org/stable/c/c0b29d523ef363d1d7ccfb3199f0126b22a61f66 (opens in a new tab)