نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) 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? Refuse to re-try initialization if SNP is not already initialized for SNP_CONFIG. This is technically an ABI break: before if SNP initialization failed it could be transparently retriggered by this ioctl, and if no VMs were running, everything worked fine. Hopefully this is enough of a corner case that nobody will notice, but someone does, there are a few options:
do something like symbol_get() for kvm and refuse to initialize if KVM is loaded
check each cpu's HSAVE_PA for non-zero data before re-initializing
once initialization has failed, continue to refuse to initialize until the ccp module is unloaded
A flaw was found in the Linux kernel's crypto:ccp module. A local attacker with access to a userspace process could exploit this vulnerability. If Secure Encrypted Virtualization (SEV) initialization fails while Kernel-based Virtual Machine (KVM) is running virtual machines, the attacker can trigger a specific code path through /dev/sev input/output controls (ioctls). This can cause a system crash, leading to a Denial of Service (DoS) for the host.

