CVE-2026-98719

KVM: SEV: Nullify "have run CPUs" mask pointer when freeing it

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Nullify "have run CPUs" mask pointer when freeing it Nullify have_run_cpus when freeing the mask, particularly in the error path of __sev_guest_init(), so that KVM doesn't have to subtly use sev->active to track whether or not the mask has been freed. As pointed out by Sashiko, blindly freeing the mask in sev_vm_destroy() results in a double-free if the mask is freed if __sev_guest_init() fails. Throw the logic in a helper as nullifying the pointer is frustratingly difficult and weird due to have_run_cpus being a single-entry array when CPUMASK_OFFSTACK=n. Deliberately don't use CPUMASK_VAR_NULL, as it's not directly assignable when the cpumask is on-stack, e.g. requires using a local variable and a memcpy(), which is beyond ridiculous. Furthermore, while clearing the on-stack bitmask is an unnecessary and arguably unwanted side effect, KVM absolutely relies on '0' being the "null" value given that the struct is zero-allocated. Opportunistically add an alloc() helper to pair with free(); there are just enough call sites to make doing so worthwhile.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.166% likely to be exploited in the next 30 days, higher than 5.915% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 6aef7cf800098749ff5d660222efaf6e01e98c09 up to but excluding b1de3ebf59507e0edacaa5cfa2225bc1869e1b63 (affected)
  • 9784e5ca91b37b387f3f414af4340c54f7a63566 up to but excluding 0fbc7fec2242de6c3dcea6de55573c428e820173 (affected)
  • 12c1f6e03f944e399bd2c88441dca5dc702b95a5 up to but excluding 8abbc76120a74bfba1851bd97528099d715e45c6 (affected)
LinuxLinux
  • Default status: unaffected
  • 6.18.55 up to but excluding 6.18.56 (affected)
  • 7.2.9 up to but excluding 7.2.10 (affected)

Timeline

  1. 18 Oct 2026 Published

References