Database/Firmware, BMC & network fabric

Linux KVM/SEV - vCPU locking when synchronizing VMSAs for SNP launch finish: KVM did not lock all vCPUs
Impact
KVM did not lock all vCPUs while synchronising and encrypting VMSAs at SNP launch finish, so vCPU state could change underneath the encryption step. The VMSA is what the launch measurement covers; if it can move while being measured, the attestation you hand the tenant does not necessarily describe the VM that actually ran.
Who can reach it
Through the KVM SNP launch path, from the VMM process.
What to do
Fixed in the Linux kernel. Take the distro kernel update (RHEL/Rocky, Ubuntu, SLES) and reboot the host - no firmware, VBIOS or AGESA step. On a GPU fleet this is a cordon, drain and rolling reboot; plan it as normal kernel maintenance.
References
Related entries
- Linux KVM - VMSA sync on an already-launched SEV vCPU: KVM allowed synchronising vCPU state into the VMSACVE-2026-31593 · Linux KVM - VMSA sync on an already-launched SEV vCPUMedium
- Linux bnxt_en driver (backing store type from firmware response): A second firmware-controlled-index bug in the sameCVE-2026-43034 · Linux bnxt_en driver (backing store type from firmware response)Medium
- Linux kernel smartpqi: memory leak in pqi_report_phys_luns() error paths on Smart Array controllersCVE-2026-45872 · Linux kernel smartpqi (pqi_report_phys_luns() error paths)Medium
- Linux kernel mlx5_ib: kernel memory leak on the RDMA data-direct sysfs path queryCVE-2026-45922 · Linux kernel mlx5_ib (GET_DATA_DIRECT_SYSFS_PATH uverbs handler)Medium
- Linux kernel mlx5_ib: UMR completion wait hangs forever when a bonded ConnectX pair is resetCVE-2026-45973 · Linux kernel mlx5_ib (RDMA device unload in LAG mode)Medium
- Linux kernel (drivers/infiniband/hw/irdma): A tenant that asks for a user QP while declaring a zero-size work-queueCVE-2026-68418 · Linux kernel (drivers/infiniband/hw/irdma)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.