CVE-2026-99712: KVM: x86: Conditionally resched when restarting REP string emulation

Published Nov 20, 2026
·
Updated

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 (NEEDRESCHED, signals, etc.) but also guest events (e.g. by checking kvmvcpuhasevents()). Unfortunately, as pointed out by Sashiko, pioinemulated()'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 kvmvcpuhasevents() or xfertoguestmodeworkpending() would introduce architecturally-incorrect, guest-visible changes.

Affected Software

7 affected componentsFixes available
linux/kernel>=2.6.35<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which environments are most likely to experience the performance impact?

KVM on x86 is affected when emulation is restarted, such as for REP-prefixed string instructions. The cost can be especially high with shadow paging, where guest writes may trigger write tracking for each write.

2

Why does the fix only conditionally reschedule instead of responding to all pending guest events?

KVM's restart behavior is required to drain the I/O port read-ahead cache and prevent duplicate I/O-port reads. Re-entering the guest merely because guest events or guest-mode work are pending could create architecturally incorrect, guest-visible behavior.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203