KVM: x86: Conditionally resched when restarting REP string emulation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c1293d2134c2d63741b197a1e5a6363894ed4bce, Kernel 41a43510f77298d147a098eb182695d0001593c8, Kernel 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5cd21917da245fbe98bd443de2c7f519b3df6814 <c1293d2134c2d63741b197a1e5a6363894ed4bce, >=5cd21917da245fbe98bd443de2c7f519b3df6814 <41a43510f77298d147a098eb182695d0001593c8, >=5cd21917da245fbe98bd443de2c7f519b3df6814 <5a5f9853a78c45927cd0814ae67c5ad8b5021bcc, >=5cd21917da245fbe98bd443de2c7f519b3df6814 <ae85ac25eb671d174811cc3101549448671fd505, =2.6.35 | c1293d2134c2d63741b197a1e5a6363894ed4bce, 41a43510f77298d147a098eb182695d0001593c8, 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc, ae85ac25eb671d174811cc3101549448671fd505 |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=2.6.35 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket