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-99712: KVM: x86: Conditionally resched when restarting REP string emulation
Date: Fri, 20 Nov 2026 06:51:38 +0100	[thread overview]
Message-ID: <2026112006-CVE-2026-99712-8147@gregkh> (raw)

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

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: Conditionally resched when restarting REP string emulation

When restarting emulation, e.g. of a REP-prefixed string instruction,
conditionally reschedule as emulating guest writes can be deceptively slow
and expensive, e.g. when shadow paging is in use and each write can trigger
write tracking.

In a perfect world, restarting emulation (or not) would be less arbitrary,
e.g. would honor not only host events (NEED_RESCHED, signals, etc.) but
also guest events (e.g. by checking kvm_vcpu_has_events()).  Unfortunately,
as pointed out by Sashiko, pio_in_emulated()'s read-ahead logic is baked
into the restart logic, as KVM relies on restarting emulation to drain the
cache and avoid duplicate reads from the I/O port.  I.e. re-entering the
guest on kvm_vcpu_has_events() or __xfer_to_guest_mode_work_pending() would
introduce architecturally-incorrect, guest-visible changes.

The Linux kernel CVE team has assigned CVE-2026-99712 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.35 with commit 5cd21917da245fbe98bd443de2c7f519b3df6814 and fixed in 6.12.118 with commit c1293d2134c2d63741b197a1e5a6363894ed4bce
	Issue introduced in 2.6.35 with commit 5cd21917da245fbe98bd443de2c7f519b3df6814 and fixed in 6.18.64 with commit 41a43510f77298d147a098eb182695d0001593c8
	Issue introduced in 2.6.35 with commit 5cd21917da245fbe98bd443de2c7f519b3df6814 and fixed in 7.3.5 with commit 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc
	Issue introduced in 2.6.35 with commit 5cd21917da245fbe98bd443de2c7f519b3df6814 and fixed in 7.4-rc2 with commit ae85ac25eb671d174811cc3101549448671fd505

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-99712
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/x86.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/c1293d2134c2d63741b197a1e5a6363894ed4bce
	https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8
	https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc
	https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505

                 reply	other threads:[~2026-11-20  5:59 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=2026112006-CVE-2026-99712-8147@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.