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=1795154488; b=yMKbWvRMRjFuTFl+lGqMC7thAVx/CEq57c4Y2rcPE/S35YlQLgX6VjWfhgqt9av+HlRc FwuMLIuuQPttCTppqNo0LEme6Bmrr9ybJSGA/QqxkHxlF+KNS9O9tGhocKFFbtfKXzINi 89FmbyhAf/SzJpVZvtKmHNrnoCqy/EOybvG7VcFPfIC8Z3txULK3RSsViiTFKJyEb+Wii aORWL10oBJcrlx3L4raTwj8sh+tMOc1rS5+mEWsHiiUz2TVARsXOD6w1ZZ1p6tEtXdfjr +AouTPifww3YM33SC7V0xZ4WtKdZubJY7+jEPg4Zpt2bvKZ4hJgPxFXIK2FQ48kfd0w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154488; 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=dqa8PkjOBlRuEw0BYjIk7cN8Yh7wzUAH035K/TDCIto=; b=ShhRGeeAvAF4m4lDcJGUndVn5bJOvVqoLdO9VxO0B8ZR+/M44qoc77xjHXd8iFe9AGDM 8vRblllow1zRRioqoFnVsehxQYLkufGvB00zz4lS6r6XRcwpizHORmfKgwR5zm9MNi8QD aNgfRrrGJGD4YD2FFdEAKubF0iivehk2QvsoFZtpcLTuWSJRnMAZRVjCjnlYCKJ9r4pks wsa2+z1rC4a+fqippa4yd8oq/2lU66k0+2BwK+mxPY5qcRN5/fgV6y1xQ4A1oCFkh/7JK JwHDMJQhs+VsLMT9hPCmtp9rIeNzSWYzkNX9ozVppI6Bhq3ba8/e1wsMtF+jxqpAZ/g== 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="Pxk/Dfcg"; 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 C4965606A521 for ; Fri, 20 Nov 2026 06:01:28 +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=Pxk/Dfcg Received: by smtp.kernel.org (Postfix) with ESMTPSA id 219C91F000C6; Fri, 20 Nov 2026 06:01:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154488; bh=dqa8PkjOBlRuEw0BYjIk7cN8Yh7wzUAH035K/TDCIto=; h=From:To:Cc:Subject:Date:Reply-To; b=Pxk/DfcgFUKBnWp9R4w/dUlBxB6Whs12UbVvczO9JsQ9fqp4rc/BBBOY5b5FfQdTF bKyQ0FMosUUhCeQXCLIyD3DxDWFjvkD4y+yxkq5OlVM2gKZ6/wfUA3MRLPcdo5C2ib JX8qKdM9jVHRCePbkTFnCEu28exgeaR2Q9Z+PGD0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99713: KVM: x86/mmu: Conditionally resched when retrying gPTE walk on A/D update failure Date: Fri, 20 Nov 2026 06:51:39 +0100 Message-ID: <2026112007-CVE-2026-99713-a49a@gregkh> X-Mailer: git-send-email 2.56.1 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=2670; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=sqkZIYGkuyFlkCsjKIBoqfBxeWRshSka8wmnJ1wTRI0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7/dPeHpp95odSUxuoY8+lPsd+Zanel1wU3CiWsvHx NLoxA2KHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAnCTVzPMFe+3j/4eyPXi/e9T 79fu4NOxOX68hGGeMdfqbusjK3cW/jcSmHpKVeTSyvOaAA== 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: x86/mmu: Conditionally resched when retrying gPTE walk on A/D update failure Conditionally reschedule when retrying a guest PTE walk because the CMPXCHG to update A/D bits failed, e.g. because a different task/vCPU modified the relevant gPTEs. On kernels without involuntary preemption of some kind, a misbehaving guest can "capture" a pCPU effectively indefinitely and trigger soft lockups by continuously modifying its gPTEs such that the result of the walk is remains valid. The Linux kernel CVE team has assigned CVE-2026-99713 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.25 with commit b3e4e63fd9ee8cd5d9047b89e0d463d5c48ee5b5 and fixed in 6.12.118 with commit 399c8c1e2ea42018960a31ef3a2e93554e50f606 Issue introduced in 2.6.25 with commit b3e4e63fd9ee8cd5d9047b89e0d463d5c48ee5b5 and fixed in 6.18.64 with commit 9c24e8e00238d7fd12808dcddb41b264f7e4918b Issue introduced in 2.6.25 with commit b3e4e63fd9ee8cd5d9047b89e0d463d5c48ee5b5 and fixed in 7.3.5 with commit 193bfab2791eedc1dbe2d61755211a2973d79138 Issue introduced in 2.6.25 with commit b3e4e63fd9ee8cd5d9047b89e0d463d5c48ee5b5 and fixed in 7.4-rc2 with commit b2691b3a6cd230209736c89684dab90d939aa56b 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-99713 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/mmu/paging_tmpl.h 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/399c8c1e2ea42018960a31ef3a2e93554e50f606 https://git.kernel.org/stable/c/9c24e8e00238d7fd12808dcddb41b264f7e4918b https://git.kernel.org/stable/c/193bfab2791eedc1dbe2d61755211a2973d79138 https://git.kernel.org/stable/c/b2691b3a6cd230209736c89684dab90d939aa56b