crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)
Sashiko notes:
> if SEV initialization fails and KVM is actively running normal VMs, could a > userspace process trigger this code path via /dev/sev ioctls (e.g., > SEV_PDH_GEN) and zero out MSR_VM_HSAVE_PA globally? Would the next VMRUN > execution for an active VM trigger a general protection fault and crash the > host?
The SNP_COMMIT command does not require the firmware to be in any particular state. Skip initializing it if it was previously uninitialized.
The SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in Table 5 as a command that is allowed in the UNINIT state, but it is in fact allowed and a future documentation update will reflect that.
From the CVE record · Linux
The Linux kernel crypto ccp driver can unnecessarily initialize SNP when a local userspace process issues an SNP_COMMIT ioctl through /dev/sev, even if SNP was previously uninitialized. The report raises a possible host-crash scenario involving failed SEV initialization and active VMs, but does not establish that outcome or specify authentication requirements.
Engineers running Linux kernels with the crypto ccp driver should check their kernel's status for this issue; affected versions were not provided.