From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DC17A4F0548 for ; Wed, 16 Sep 2026 10:41:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555318; cv=none; b=SCwjq1d+sbCfdJI0nSQWHTOseGlDBQF+6FFx6y8fHxnpv9pXJpngYB+eFx0A76I5eaMX96GqW8ujw+nmxDbXP/WoPM2Pf5yiY57AEfig5nsKOb/ruOaA44/z9EH7uUGE0E2o3yK9QXhgobiQ7+oqzC4PClxqXU+Fge4XGCY6Xmc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555318; c=relaxed/simple; bh=xnSghpUOK2jdq9HbTwsulNw6f+j5rL/Af56nI5JB5K0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=sOcfJlMQVp0rqX/wYceepK+szP+kKGy4frKTkyGMm+4udDjaOclAMk/CLEpNxF6ZXz2pFuGFDvbv5ZyKHoJQBauvzc/KHHWn/6vg5MkasjJkeTZ+Zuu5lXhKoMSjrvfPdSfuTjF4hNDylKCb11i8K+Hqb+i9yp6jIkCTI5Ywacw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=MPHkqKR6; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="MPHkqKR6" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83CAF1F0089B; Wed, 16 Sep 2026 10:41:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789555287; bh=36yemOoDaPP+xPcKWa9FBIq4Ca6qocd6muA6d5UVa1c=; h=From:To:Cc:Subject:Date:Reply-To; b=MPHkqKR6GNOMZ990EzCCkcX0tOub9R0G+1Od3FMiNrKX/qy+9eDQwKjKA3NmLRmH+ EwSDVw3buqw0de5+aACQkn/im5LrP+5FETwSyAxIHbjcgSdBSlnSiZ7eNrgmmL35L7 YI3J7kcX2I8QfL6aJ38QNqnUeLF0Sb+0WUfbpmus= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter Date: Wed, 16 Sep 2026 11:31:00 +0100 Message-ID: <2026091645-CVE-2026-89930-be2e@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4286; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Dpmc6ruo6ov+z7UuZzTOAhZ0j4MPJR4Mg0LJ2EtjL+Y=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8mdmsrMVMH2PVdTfq+yQrhaVKcP5iiUxhU+e80bwg zuGjx92xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwES23WCYK5hbXi3tnTl1lYYU r4NCyz6hIrm5DPNdgi425Of02Agx6/h4Bs6/7Lm/0Q0A 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: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits (through __nested_vmx_vmexit()), but not if a nested VM-Enter fails (e.g. due to failed VMCS checks in nested_vmx_enter_non_root_mode()). However, it is possible that KVM had queued TLB flushes that need to be performed, even if the nested VM-Enter was not successful. For example, if VPID is disabled for L2 (via nested_vmx_transition_tlb_flush(), or if via the MSR load lists, as the SDM says: If any MSR is being loaded in such a way that would architecturally require a TLB flush, the TLBs are updated so that, after VM entry, the logical processor will not use any translations that were cached before the transition. The SDM is unclear about when the TLB flush should occur, and whether or not a failed VM entry would flush the TLB, so it is safer to always do the TLB flush in this case. More concretely, KVM also updates the last VPID L1 used for L2 in nested_vmx_transition_tlb_flush() (i.e. last_vpid), even if the VM entry ultimately fails. With the current code, KVM could miss a TLB flush if L1 changes L2's VPID, then does a failed VM entry followed by a successful one, as the failed VM entry would update last_vpid but not actually flush the TLB. Servicing local TLB flushes on failed VM entries makes sure that the TLB is always flushed when last_vpid is updated. The Linux kernel CVE team has assigned CVE-2026-89930 to this issue. Affected and fixed versions =========================== Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 5.15.221 with commit c0c66cd575e31218da6a7d104c6ef80b0830b60c Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 6.1.188 with commit 1025b938dc439b75c720a568a855a13eeb245686 Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 6.6.157 with commit 312cdb6d8940827dea63a7a52fb714a5049f06d1 Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 6.12.110 with commit f74fccdf4f7fb0780cd84944108d35f3d9dc46a7 Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 6.18.51 with commit c43563e7518e65ec6ccaa6a65f84c5af5ca5d379 Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 7.2.5 with commit 62c3ee4c9f0e2efef5157358b3549e50ede96d73 Issue introduced in 4.4 with commit 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and fixed in 7.3-rc1 with commit 05a0b701d1089fb57beeb8982f23c3bbafe0fa8b 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-89930 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/vmx/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/c0c66cd575e31218da6a7d104c6ef80b0830b60c https://git.kernel.org/stable/c/1025b938dc439b75c720a568a855a13eeb245686 https://git.kernel.org/stable/c/312cdb6d8940827dea63a7a52fb714a5049f06d1 https://git.kernel.org/stable/c/f74fccdf4f7fb0780cd84944108d35f3d9dc46a7 https://git.kernel.org/stable/c/c43563e7518e65ec6ccaa6a65f84c5af5ca5d379 https://git.kernel.org/stable/c/62c3ee4c9f0e2efef5157358b3549e50ede96d73 https://git.kernel.org/stable/c/05a0b701d1089fb57beeb8982f23c3bbafe0fa8b