CVE-2026-98715

published 18 Oct 2026 · updated 20 Nov 2026

KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd873c3d1b5240e80365f09e758e8c96b88a7cdb, Kernel 60d93c27859fb3ec5b5a689e24de303f166477d0, Kernel bfe48e689ba011d3d6cf8adcca03072aa0430133 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN Don't reset the VMCB's TLB control back to "do nothing" on a failed VMRUN, as empirical testing shows that the CPU performs the requested TLB flush if and only if VMRUN is successful, i.e. clearing TLB control on a failed VMRUN effectively drops a TLB flush. Explicitly track the need to flush all ASIDs on a per-CPU basis, as the ASID reuse condition is tied to the pCPU, not to the vCPU. As a bonus, this also obviates the need to avoid clobbering FLUSH_ALL_ASID with TLB_CONTROL_FLUSH_ASID, e.g. in svm_flush_tlb_asid(). Deliberately don't bother saving/restoring the "old" tlb_ctl on failure, in quotes because it's not exactly the old tlb_ctl, it's the tlb_ctl from after pre_svm_run(), but before updating tlb_ctl for flush_all_asids. If VMRUN fails and TLB_CONTROL_FLUSH_ALL_ASID is forced, then the next successful run of the VMCB *may* unnecessarily flush all ASIDs, which strictly speaking could result in noisy neighbor issues. However, the fact that new_asid() is already guest-triggerable, because of KVM's flawed behavior of clearing the ASID on emulated INIT, means that a guest can already trigger a flush of all ASIDs at roughly the same rate. And once KVM stops clobbering the ASID on emulated INIT, *or* assigns a static ASID to each vCPU, this flaw goes away.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=38e5e92fe8c02a8766459d505423b855caf9af1f <fd873c3d1b5240e80365f09e758e8c96b88a7cdb, >=38e5e92fe8c02a8766459d505423b855caf9af1f <60d93c27859fb3ec5b5a689e24de303f166477d0, >=38e5e92fe8c02a8766459d505423b855caf9af1f <bfe48e689ba011d3d6cf8adcca03072aa0430133, >=38e5e92fe8c02a8766459d505423b855caf9af1f <f2bd7cf6a83e49c710e2b93d3064fa0ebb7e0006, =2.6.38fd873c3d1b5240e80365f09e758e8c96b88a7cdb, 60d93c27859fb3ec5b5a689e24de303f166477d0, bfe48e689ba011d3d6cf8adcca03072aa0430133, f2bd7cf6a83e49c710e2b93d3064fa0ebb7e0006
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.2.10, >=2.6.38 <6.12.1176.18.61, 7.2.10, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98715 severity on Zeptric[![CVE-2026-98715](https://zeptric.io/badge/cve/CVE-2026-98715.svg)](https://zeptric.io/cve/CVE-2026-98715)