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 BAF7D4EC675 for ; Wed, 16 Sep 2026 10:41:49 +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=1789555322; cv=none; b=szMdGMEzrPpbIu3qznRjeME8eugj4t62PDU6ocLMLyDfNornYE26GhGXAXvb0EnjwbJD0pIOVc/kRCMrqnjeCF/vJQi+U5n2AipXjYX6+SxODowCp/iF5PVOBN3tdp1f4w8zPkCss0Pyt6RsNsuZAzcqsgDJqCq+GgwS4W8/K94= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555322; c=relaxed/simple; bh=gcGoOi7WhtA5jdTWG+CXQEezJelpxeZNUJErSXPK/TA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=aVJVUQ/tWwF0iQGwjyAUz0t1XxJBwMul1WQnnya7jowSEMim1npTrSA+n0i+FyZAMF9hdS2tb3SuE5vMvRzv1q2Wpx3s3jO50phLd/akYckg97kX7FTlUr2Hp1kPKA4+JQ+cWT4yBINiBWP5ncNVxyyDHaBre7SKW0Mg5V+Cfpo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=thQJab9C; 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="thQJab9C" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CFCF11F00899; Wed, 16 Sep 2026 10:41:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789555305; bh=0OasQ1cHfoWKS6VbVmLKwKHQC+RwlFikSPEyPr1+ux4=; h=From:To:Cc:Subject:Date:Reply-To; b=thQJab9CzEWTA8cwq18qhfNkHn3SxWMoqaz0q1371E18pOpQoPN2oQsKRKluhgRFn cQUorm96HFFB3CH+IIMT/7dr+77VP9E2X8xyKWfOArEmQBhBnMWsi95FXtNKIOvWxh jVIf+Xs1VBmVPbIKKYaVs5ZGtLJPz0+eh7m/2vRo= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89932: KVM: nVMX: Always flush vpid02 on first use Date: Wed, 16 Sep 2026 11:31:02 +0100 Message-ID: <2026091645-CVE-2026-89932-1a30@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=3034; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=tyrDZ/1NuoYHXP+SiBzbpPWR/+E+BmQvtIwtmAsOsj0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8md23L1SsJq9WjiJR/Lw4qNTGX3tYnMEpU/dfcXZe +HWP9O/HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRuA0M83M3Pptraf9eb0+v 6F05+YXLbEOn1zEsmMVR9jS71/jwj2fKK1vZ7p/Y/qXxCAA= 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: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02. nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with a different vCPU (or a completely different VM). Note that last_vpid is already being initialized as 0 when the vCPU is created, but it is not reset when vpid02 is freed on VMXOFF. Hence, the problem can only occur if L1 does VMXOFF -> VMXON, runs an L2, and KVM happens to reuse a VPID that has TLB entries on the physical CPU. The Linux kernel CVE team has assigned CVE-2026-89932 to this issue. Affected and fixed versions =========================== Fixed in 5.15.221 with commit 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 Fixed in 6.1.188 with commit 8bc609999ec223089fec8d74c7de27d689606b36 Fixed in 6.6.157 with commit 62604376c313178811375f40a282fc2a46cd2311 Fixed in 6.12.110 with commit 8b98d662ab24f34710a56e03bc9169e4a5508606 Fixed in 6.18.51 with commit 22dfcc22c95e91295119a1c3b469816ce44c4804 Fixed in 7.2.5 with commit 121991d150735f3c0f7401678ce4d35c5b4ac898 Fixed in 7.3-rc1 with commit f0772389413dce9657c7d6950abf3edbbd511356 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-89932 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/26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 https://git.kernel.org/stable/c/8bc609999ec223089fec8d74c7de27d689606b36 https://git.kernel.org/stable/c/62604376c313178811375f40a282fc2a46cd2311 https://git.kernel.org/stable/c/8b98d662ab24f34710a56e03bc9169e4a5508606 https://git.kernel.org/stable/c/22dfcc22c95e91295119a1c3b469816ce44c4804 https://git.kernel.org/stable/c/121991d150735f3c0f7401678ce4d35c5b4ac898 https://git.kernel.org/stable/c/f0772389413dce9657c7d6950abf3edbbd511356