CVE-2026-99712
Severity unknownNo known exploitationFix availableKVM: x86: Conditionally resched when restarting REP string emulation
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 11% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 5cd21917da245fbe98bd443de2c7f519b3df6814 before 41a43510f77298d147a098eb182695d0001593c8 | 41a43510f77298d147a098eb182695d0001593c8 | CVE Program |
| Linux | Linux | from 5cd21917da245fbe98bd443de2c7f519b3df6814 before 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc | 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc | CVE Program |
| Linux | Linux | from 5cd21917da245fbe98bd443de2c7f519b3df6814 before ae85ac25eb671d174811cc3101549448671fd505 | ae85ac25eb671d174811cc3101549448671fd505 | CVE Program |
| Linux | Linux | from 5cd21917da245fbe98bd443de2c7f519b3df6814 before c1293d2134c2d63741b197a1e5a6363894ed4bce | c1293d2134c2d63741b197a1e5a6363894ed4bce | CVE Program |
| Linux | Linux | 2.6.35 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 2.6.35 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8 (opens in a new tab)
- https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc (opens in a new tab)
- https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505 (opens in a new tab)
- https://git.kernel.org/stable/c/c1293d2134c2d63741b197a1e5a6363894ed4bce (opens in a new tab)