CVE-2026-98715

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

Description

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.

Key facts

Published
18 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.221% likely to be exploited in the next 30 days, higher than 12.762% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 38e5e92fe8c02a8766459d505423b855caf9af1f up to but excluding bfe48e689ba011d3d6cf8adcca03072aa0430133 (affected)
  • 38e5e92fe8c02a8766459d505423b855caf9af1f up to but excluding f2bd7cf6a83e49c710e2b93d3064fa0ebb7e0006 (affected)
  • 38e5e92fe8c02a8766459d505423b855caf9af1f up to but excluding fd873c3d1b5240e80365f09e758e8c96b88a7cdb (affected)
  • 38e5e92fe8c02a8766459d505423b855caf9af1f up to but excluding 60d93c27859fb3ec5b5a689e24de303f166477d0 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.38 (affected)
  • 0 up to but excluding 2.6.38 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.61 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References