PT-2026-152592

CVE-2026-99712

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾