CVE-2026-99712
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.
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00168
- Cve id
- CVE-2026-99712
- First seen by Signal
- 2026-11-20T07:38:10+00:00
- Name
- CVE-2026-99712
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-20T06:18:07.393
- Last modified
- 2026-11-20T06:18:07.393
- Epss percentile
- 0.06181
Related research
Explore deeper with Ninja Signal's threat intelligence graph