VulnWatch by ve1ve2

CVE-2026-98715

unknown awaiting NVD score — see report severities below NVD ↗CVE.org ↗

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* unnecessa

CVSS:
—
EPSS:
0.22% (percentile 12.7)
Published:
Modified:
First seen:
NVD status:
Received
Aliases:
CVE-2026-100080, CVE-2026-100081, CVE-2026-100082, CVE-2026-89866, CVE-2026-92499, CVE-2026-98176, CVE-2026-98177, CVE-2026-98180, CVE-2026-98228, CVE-2026-98408, CVE-2026-98439, CVE-2026-98449, CVE-2026-98466, CVE-2026-98674, CVE-2026-98682, CVE-2026-98683, CVE-2026-98684, CVE-2026-98685, CVE-2026-98714, CVE-2026-98786, CVE-2026-98853, CVE-2026-98863, CVE-2026-98920, CVE-2026-98978, CVE-2026-98989, CVE-2026-98996, CVE-2026-99021, CVE-2026-99026, CVE-2026-99076, CVE-2026-99086, CVE-2026-99087, CVE-2026-99109, CVE-2026-99122, CVE-2026-99146, CVE-2026-99172, CVE-2026-99270, CVE-2026-99271, CVE-2026-99273, CVE-2026-99274, CVE-2026-99281, CVE-2026-99282, CVE-2026-99283, CVE-2026-99286, CVE-2026-99287, CVE-2026-99288, CVE-2026-99290, CVE-2026-99292, CVE-2026-99295, CVE-2026-99296

JSON

Reports (2)