From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795098791; b=hxIlBHchZJFKn1xqd3OPx40bO57fZivTUG0d1ZE1HROyii+Lj/bEC7V0qyMhlkscIUqx yFLN9P5frHXyCBCzdL875Pi11FGK6Vry1YIObY71ol98fgZTgio053r/7hKnwPDjIlJp3 c0tzdDSLVDG86d5QSd86H9yZP3D5JQbjHPxAqagAtwpKHGTv4ueWtrGi6H+CQUC6Brmsg gQGWBPayTKIgthchOOZa19/8iRY4g9I2Z0/6yTdbvhh2j7dR6XQi6NYPsKFGtyAChrVgX TYth1rQJKTL0eI94YlNB/PEe4bhI7pNAH/hUpzWiZ1SA+VAzCxUHNEs71PR1F5L0ByQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795098791; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=c2lXCC10hhqXl4FIOZIrSuDgk0FpouPZwsRXaKdbzYw=; b=Qu5S/PiO9NgGKBm1jIRZD7Grt61eaUHlqUdpVvsmA71dPVRuxaBdxigsHn0PlyWacsLC aeKZ8Us32HtOkjQzpo4dXa21onkdk28uHpM+LY+wLiOfAXEJacFwQFsGHjH2Nb+9jz+cq P4xX5RsiQhHKWbLBQOyX2ocRyjpez7ekXmxWAuOPPbk32hh52kIPY4Y9boY/njM1p2f0U P1PYgZYGx8cxvlCyiy0pRyyOR3ROALZTsWhrUUMMD5NiWw2qGsGjtobOJ55VcdmaM9Kqd JI9u9DBJFbP8LjAkjXX5f+gouoJaABPpFeR5eO3nIQWsgJqtZ7mdQQHfbAz67qW2kYA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=v0J0lXa0; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9DDC8606A32A for ; Thu, 19 Nov 2026 14:33:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=v0J0lXa0 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5E3821F00925; Thu, 19 Nov 2026 14:33:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795098791; bh=c2lXCC10hhqXl4FIOZIrSuDgk0FpouPZwsRXaKdbzYw=; h=From:To:Cc:Subject:Date:Reply-To; b=v0J0lXa0sZPZNTn72HUqtIYyRJWFoy5DKQN1i7gIYnckSeCboTXs+Hc5gAIL/qenq xUJfdhTmm/QEQOI+hhQ/QA+9POuSAcYnSJULCCYzcem6fKyLsj3VwfF5nrl7Dx2V4+ 0LEdbjG45lcU4mK5Z7rhd86hG5eX7drXfO/VMaMg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99345: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0 Date: Thu, 19 Nov 2026 15:24:03 +0100 Message-ID: <2026111947-CVE-2026-99345-e572@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3392; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YpbwrJPFQy9Ci1fBg8hKNkI4SI8uMdSxZs6pjQ6CRsY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2Yr5DN0u1SxV19kiPSnz79FiWc0pXPYV/2QTg8I27 OLakL24I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbCPIFhfvUPluD+iZun6+cd Kjp64bxJpNXk1QwLdu9MN//nwZLitv/VxPt33m+c9uKNHAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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