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.
Published: 2026-10-18
Score: 3.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Use‑After‑Free leading to memory corruption
Action: Apply Patch
AI Analysis

Impact

The vulnerability arises when the Linux kernel’s KVM SEV module frees a CPU mask during virtual‑machine destruction even if the VM has migrated to a non‑encrypted state. This incorrect deallocation is a classic use‑after‑free situation that can corrupt kernel memory or expose sensitive data. The main consequence is potential host crashes, instability, or data leakage, impacting availability, confidentiality, and integrity of the host system.

Affected Systems

Linux operating systems that compile the upstream kernel with SEV support are affected, regardless of distribution. Since the vulnerability is tied to the SEV code path, any kernel that enables SEV encryption for its guests will contain the defect. No specific version is listed, so all current kernels that support SEV should be considered vulnerable until a patch is applied.

Risk and Exploitability

The CVSS base score is 3.3, indicating low severity. The EPSS score is reported as < 1%, suggesting a very low likelihood of exploitation. The flaw is not listed in CISA’s KEV catalog. Exploitation would require influence over VM destruction or intra‑host migration, typically a local privileged user or a malicious guest capable of triggering the faulty path. Given the low score and lack of public exploits, the overall risk is considered low to moderate, but in environments running SEV VMs the vulnerability still poses a potential risk to availability and memory integrity.

Generated by OpenCVE AI on October 23, 2026 at 07:03 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that corrects the SEV machine‑destruction deallocation bug.
  • If the kernel cannot be updated immediately, disable SEV support on hosts that do not require it to eliminate the vulnerable code path.
  • Reboot the host after applying the patch or disabling SEV to clear any stale kernel objects.
  • If a patch is not yet available, monitor the KVM host for unexpected kernel panics or memory corruption and consider isolating untrusted guests from accessing VM‑destruction APIs.

Generated by OpenCVE AI on October 23, 2026 at 07:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 23 Oct 2026 00:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Tue, 20 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Low


Sun, 18 Oct 2026 17:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Sun, 18 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
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.
Title KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:20:10.096Z

Reserved: 2026-09-25T10:25:14.351Z

Link: CVE-2026-98472

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:16:57.697

Modified: 2026-10-19T10:18:57.743

Link: CVE-2026-98472

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98472 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T07:15:17Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime