Answer in brief
CVE-2026-98472 records a Unknown severity vulnerability in KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV. 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.
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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6f38f8c574642a822f2e85f079fa29a49176c49c <6aef7cf800098749ff5d660222efaf6e01e98c09 || >=6f38f8c574642a822f2e85f079fa29a49176c49c <9784e5ca91b37b387f3f414af4340c54f7a63566 || >=6f38f8c574642a822f2e85f079fa29a49176c49c <12c1f6e03f944e399bd2c88441dca5dc702b95a5 | 6aef7cf800098749ff5d660222efaf6e01e98c09, 9784e5ca91b37b387f3f414af4340c54f7a63566, 12c1f6e03f944e399bd2c88441dca5dc702b95a5 |
| Linux/Linuxgeneric | 6.17 | Not reported |
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: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV Unconditionally free SEV's "have run CPUs" cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when "converting" the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y. Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that's kind of a moot point since any such bugs would show up even if sev->active is never set. I.e. KVM must get that side of things correct. But, that's not a great reason to add more code just to make things marginally less robust.
Quoted source text, attributed separately from HOL analysis.