CVE-2026-64310crypto: ccp - Do not initialize SNP for SEV ioctls
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for SEV ioctls 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? sev_move_to_init_state() is called for ioctls requiring only SEV firmware: SEV_PEK_GEN, SEV_PDH_GEN, SEV_PEK_CSR, SEV_PEK_CERT_IMPORT, and SEV_PDH_CERT_EXPORT. After the firmware command, it does SEV_SHUTDOWN on the SEV firmware. Since these commands do not require SNP to be initialized, skip it by calling __sev_platform_init_locked() which only initializes the SEV firmware. This way SNP is not Initialized at all, and HSAVE_PA is not cleared. The previous code saved any SEV initialization firmware error to init_args.error and then threw it away and hardcoded the return value of INVALID_PLATFORM_STATE regardless of the real firmware error. This patch changes it to surface the underlying error, which is hopefully both more useful and doesn't cause any problems. Note that it is still safe to call __sev_firmware_shutdown() directly: it calls __sev_snp_shutdown_locked(), which skips SNP shutdown if SNP was not initialized.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 before 5181e88da99c3d1d41e25db3472a62b8d4b42cdd; from ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before 9e983d0a74a6a2348e4ce61647ec8a4dfbe198ac; from ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before d51207735e7c224cf591fa260c557a451a69a5cf; from ceac7fb89e8da465aec3ac3c20477f912f5c3a6c before fb1758e74b8061aacfbce7bbb7a7cc650537e167; from 6.12.75 before 6.12.96 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.12.75 before 6.12.96; from 6.16 before 6.18.39; from 6.19 before 7.1.4 | NVD |
References
- https://git.kernel.org/stable/c/5181e88da99c3d1d41e25db3472a62b8d4b42cddpatch
- https://git.kernel.org/stable/c/9e983d0a74a6a2348e4ce61647ec8a4dfbe198acpatch
- https://git.kernel.org/stable/c/d51207735e7c224cf591fa260c557a451a69a5cfpatch
- https://git.kernel.org/stable/c/fb1758e74b8061aacfbce7bbb7a7cc650537e167patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.