Skip to main content
VulnerabilityPublished Updated

CVE-2026-31591: Linux kernel · KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cb923ee6a80f4e604e6242a4702b59251e61a380 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in cb923ee6a80f4e604e6242a4702b59251e61a380, c87938fc7d99a06a7e5477c45b4e5a4148f85d66, 30fd9d8c82087742168db779929d8be0459b0716 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to cb923ee6a80f4e604e6242a4702b59251e61a380, c87938fc7d99a06a7e5477c45b4e5a4148f85d66, 30fd9d8c82087742168db779929d8be0459b0716 or 4df77742e8b9a6b935bdf46f02fd0aca4d4ee7f5.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ad27ce155566f2b4400fa865859834592bd18777, < cb923ee6a80f4e604e6242a4702b59251e61a380
Fixed in
  • cb923ee6a80f4e604e6242a4702b59251e61a380
LinuxLinuxAffected
  • ≥ ad27ce155566f2b4400fa865859834592bd18777, < c87938fc7d99a06a7e5477c45b4e5a4148f85d66
Fixed in
  • c87938fc7d99a06a7e5477c45b4e5a4148f85d66
LinuxLinuxAffected
  • ≥ ad27ce155566f2b4400fa865859834592bd18777, < 30fd9d8c82087742168db779929d8be0459b0716
Fixed in
  • 30fd9d8c82087742168db779929d8be0459b0716
LinuxLinuxAffected
  • ≥ ad27ce155566f2b4400fa865859834592bd18777, < 4df77742e8b9a6b935bdf46f02fd0aca4d4ee7f5
Fixed in
  • 4df77742e8b9a6b935bdf46f02fd0aca4d4ee7f5
LinuxLinuxAffected
  • =6.11
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish Lock all vCPUs when synchronizing and encrypting VMSAs for SNP guests, as allowing userspace to manipulate and/or run a vCPU while its state is being synchronized would at best corrupt vCPU state, and at worst crash the host kernel. Opportunistically assert that vcpu->mutex is held when synchronizing its VMSA (the SEV-ES path already locks vCPUs).

References

Community reviews

Loading reviews…