Description
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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 to < 74768f73854d647a6462f252dc8782ab8a835211affectedceac7fb89e8da465aec3ac3c20477f912f5c3a6c to < 7a361c74bb12f3398c388905f1d325be642cd36eaffectedceac7fb89e8da465aec3ac3c20477f912f5c3a6c to < 67ed191b4c8bdf432a3f32d1eb302880b4795cd1affectedceac7fb89e8da465aec3ac3c20477f912f5c3a6c to < 5a1364da2f04217a36e2fdfa2db4ee025b383a20affected6.12.75 to < 6.12.96affected
Linux Linux
Default version status: affected
6.16affected0 to < 6.16unaffected6.12.96 to ≤ 6.12.*unaffected6.18.39 to ≤ 6.18.*unaffected7.1.4 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected