In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Conditionally...
🔗 CVE IDs covered (1)
📋 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.
🔗 References (6)
- https://nvd.nist.gov/vuln/detail/CVE-2026-99712
- https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8
- https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc
- https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505
- https://git.kernel.org/stable/c/c1293d2134c2d63741b197a1e5a6363894ed4bce
- https://github.com/advisories/GHSA-3w5c-468g-wm9v