CVE-2026-31591 Affecting linux-qemu-6.18 package, versions <6.18.31-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.12% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-LINUXQEMU618-16727673
  • published17 May 2026
  • disclosed24 Apr 2026

Introduced: 24 Apr 2026

CVE-2026-31591  (opens in a new tab)

How to fix?

Upgrade Chainguard linux-qemu-6.18 to version 6.18.31-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream linux-qemu-6.18 package and not the linux-qemu-6.18 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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).

CVSS Base Scores

version 3.1