1.8

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

Received
AliasesDEBIAN-CVE-2026-98715UBUNTU-CVE-2026-98715
Published 18-10-2026Last modified 10-11-2026

Vulnerability summary

CVE-2026-98715 is a low (CVSS 1.8) vulnerability in linux. EPSS estimates a 0.22% chance of exploitation in the next 30 days, higher than 12.9% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 1.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
1.8/10
010
Low · v4.0 (OSV · Ubuntu), selected by version preference
EPSS score
0.22%
0%100%
Low · +0.03 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 7 · Related 6

Timeline

  1. 18-10-2026
    PublishedVulnerability first disclosed.
  2. 10-11-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

1 score · 1 source · 1 version

EPSS trend

Probability

0.22%

Chance of exploitation in the next 30 days

Percentile

13%

Versus all other CVEs

30-day change

Increase +0.03 pp

From 0.19% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, administrative account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu169 products
  • linuxAll versions (No fix recorded) | < 7.0.0-43.43
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 7.0.0-1017.18
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian1 product
  • linuxAll versions (No fix recorded) | < 6.12.117-1 | < 7.2.10-1
Linux1 product
  • linux≥ 38e5e92fe8c02a8766459d505423b855caf9af1f, < bfe48e689ba011d3d6cf8adcca03072aa0430133 | ≥ 38e5e92fe8c02a8766459d505423b855caf9af1f, < f2bd7cf6a83e49c710e2b93d3064fa0ebb7e0006 | ≥ 38e5e92fe8c02a8766459d505423b855caf9af1f, < fd873c3d1b5240e80365f09e758e8c96b88a7cdb | ≥ 38e5e92fe8c02a8766459d505423b855caf9af1f, < 60d93c27859fb3ec5b5a689e24de303f166477d0 | 2.6.38

3 vendors · 171 products

References

13 links
Show all 13 references