Answer in brief
CVE-2026-98714 records a Unknown severity vulnerability in KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8676b29d186fcb5c1251d8152fc91d19421e5600 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e27fc915c8f575ab5630e27d97465c2077d4b9d1 || >=0 <7.2.10 | 8676b29d186fcb5c1251d8152fc91d19421e5600, e27fc915c8f575ab5630e27d97465c2077d4b9d1, 7.2.10 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD: there's no explicit architectural guarantee about the behavior in the presence of VMRUN failures. So the best thing to do would be to assume that if VMRUN fails, the actions requested in the control fields may not have been performed.
Quoted source text, attributed separately from HOL analysis.