Live › vulnerability › CVE-2026-98472
Go to dashboardIn the Linux KVM SEV code, the "have run CPUs" cpumask is not freed during VM destruction when an SEV VM has been converted to a non-SEV VM by intra-host migration. The sources describe a resource leak and do not state a confirmed attacker capability.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Hosts running Linux with KVM hypervisor support that run SEV or SEV-ES guests and perform intra-host migration of those guests. Hosts without KVM SEV guests are unlikely to be affected. The sources do not give further detail.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98472")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.