Description (CNA)
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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 before 74768f73854d647a6462f252dc8782ab8a835211; affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before 7a361c74bb12f3398c388905f1d325be642cd36e; affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before 67ed191b4c8bdf432a3f32d1eb302880b4795cd1; affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before 5a1364da2f04217a36e2fdfa2db4ee025b383a20; affected 6.12.75 before 6.12.96 |
| Linux / Linux | affected 6.16; unaffected 0 before 6.16; unaffected 6.12.96 through 6.12.*; unaffected 6.18.39 through 6.18.*; unaffected 7.1.4 through 7.1.*; unaffected 7.2 through * |
CWE
No CWE identifiers supplied.