All reports
Low

kernel: KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98472

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) AMD SEV (Secure Encrypted Virtualization) implementation. This flaw allows a local user with permissions to manage virtual machines to cause a denial of service (DoS) through memory exhaustion. When an SEV guest is destroyed after undergoing an intra-host migration, the kernel fails to release allocated CPU tracking memory, resulting in an unrecoverable memory leak each time a migrated guest is terminated.