CVE-2026-64310

published 25 Jul 2026 · updated 17 Nov 2026

crypto: ccp - Do not initialize SNP for SEV ioctls

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fb1758e74b8061aacfbce7bbb7a7cc650537e167, Kernel 6.18.39, Kernel 7.1.4 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <fb1758e74b8061aacfbce7bbb7a7cc650537e167, >=6.16 <6.18.39, >=6.19 <7.1.4, >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <9e983d0a74a6a2348e4ce61647ec8a4dfbe198ac, >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <d51207735e7c224cf591fa260c557a451a69a5cf, >=6.12.75 <6.12.96, =6.16, >=1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 <5181e88da99c3d1d41e25db3472a62b8d4b42cddfb1758e74b8061aacfbce7bbb7a7cc650537e167, 6.18.39, 7.1.4, 9e983d0a74a6a2348e4ce61647ec8a4dfbe198ac, d51207735e7c224cf591fa260c557a451a69a5cf, 6.12.96, 5181e88da99c3d1d41e25db3472a62b8d4b42cdd
linux-kernel: Kernel>=6.12.75 <6.12.96, >=6.16.0 <6.18.39, >=6.19.0 <7.1.46.12.96, 6.18.39, 7.1.4

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64310 severity on Zeptric[![CVE-2026-64310](https://zeptric.io/badge/cve/CVE-2026-64310.svg)](https://zeptric.io/cve/CVE-2026-64310)