All of lore.kernel.org
 help / color / mirror / Atom feed
* CVE-2026-99345: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0
@ 2026-11-19 14:24 Greg Kroah-Hartman
  0 siblings, 0 replies; only message in thread
From: Greg Kroah-Hartman @ 2026-11-19 14:24 UTC (permalink / raw)
  To: linux-cve-announce; +Cc: Greg Kroah-Hartman

From: Greg Kroah-Hartman <gregkh@kernel.org>

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.

The Linux kernel CVE team has assigned CVE-2026-99345 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.8 with commit cc440cdad5b7a4c1de12dace725209eb3e0cf663 and fixed in 6.12.118 with commit c0b29d523ef363d1d7ccfb3199f0126b22a61f66
	Issue introduced in 5.8 with commit cc440cdad5b7a4c1de12dace725209eb3e0cf663 and fixed in 6.18.64 with commit 98362865bb626bb5e76cede98555d7cd4fefc016
	Issue introduced in 5.8 with commit cc440cdad5b7a4c1de12dace725209eb3e0cf663 and fixed in 7.3.2 with commit 81c460713ca62fa33ee1241fda1ddaf099facb32
	Issue introduced in 5.8 with commit cc440cdad5b7a4c1de12dace725209eb3e0cf663 and fixed in 7.4-rc1 with commit 5dc500a354cc8e109df678076ae3488094649468

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99345
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	arch/x86/kvm/svm/nested.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/c0b29d523ef363d1d7ccfb3199f0126b22a61f66
	https://git.kernel.org/stable/c/98362865bb626bb5e76cede98555d7cd4fefc016
	https://git.kernel.org/stable/c/81c460713ca62fa33ee1241fda1ddaf099facb32
	https://git.kernel.org/stable/c/5dc500a354cc8e109df678076ae3488094649468

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-11-19 14:33 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-19 14:24 CVE-2026-99345: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0 Greg Kroah-Hartman

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.