All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
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	[thread overview]
Message-ID: <2026112007-CVE-2026-99713-a49a@gregkh> (raw)

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

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

                 reply	other threads:[~2026-11-20  6:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026112007-CVE-2026-99713-a49a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.