Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99712· Low

Not known to be exploited · fixed in c1293d2134c2d63741b197a1e5a6363894ed4bce : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Low

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in c1293d2134c2d63741b197a1e5a6363894ed4bce, ae85ac25eb671d174811cc3101549448671fd505, 41a43510f77298d147a098eb182695d0001593c8 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to c1293d2134c2d63741b197a1e5a6363894ed4bce, ae85ac25eb671d174811cc3101549448671fd505, 41a43510f77298d147a098eb182695d0001593c8 or 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5cd21917da245fbe98bd443de2c7f519b3df6814, < c1293d2134c2d63741b197a1e5a6363894ed4bce
Fixed in
  • c1293d2134c2d63741b197a1e5a6363894ed4bce
LinuxLinuxAffected
  • ≥ 5cd21917da245fbe98bd443de2c7f519b3df6814, < ae85ac25eb671d174811cc3101549448671fd505
Fixed in
  • ae85ac25eb671d174811cc3101549448671fd505
LinuxLinuxAffected
  • ≥ 5cd21917da245fbe98bd443de2c7f519b3df6814, < 41a43510f77298d147a098eb182695d0001593c8
Fixed in
  • 41a43510f77298d147a098eb182695d0001593c8
LinuxLinuxAffected
  • ≥ 5cd21917da245fbe98bd443de2c7f519b3df6814, < 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc
Fixed in
  • 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc
LinuxLinuxAffected
  • =2.6.35
Fixed in–

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

Community reviews

Loading reviews…