Answer in brief
CVE-2026-98471 records a High severity (CVSS 7.1) vulnerability in KVM: SEV: Do cache maintenance on the source VM during intra-host migration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.
CVSS is 7.1. 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b56639318bb2be66aceba92836279714488709b4 <37dfb676fafd1eef36fe0bb649607afbb0d5521b || >=b56639318bb2be66aceba92836279714488709b4 <d4cc2dff12116a700add601c0262132cc26e1b2c || >=b56639318bb2be66aceba92836279714488709b4 <93de2a6a4b91b72607136dd656edf03fb399d27f | 37dfb676fafd1eef36fe0bb649607afbb0d5521b, d4cc2dff12116a700add601c0262132cc26e1b2c, 93de2a6a4b91b72607136dd656edf03fb399d27f |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 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: SEV: Do cache maintenance on the source VM during intra-host migration Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is "converted" to a non-SEV VM, KVM's memory reclaim flows won't trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier. Note, relying on the destination VM to do cache maintenance isn't an option as KVM doesn't require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.
Quoted source text, attributed separately from HOL analysis.