Description
In the Linux kernel, the following vulnerability has been resolved:

crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD)

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 SEV firmware docs for SNP_VLEK_LOAD note:

> On SNP_SHUTDOWN, the VLEK is deleted.

That is, the initialization/shutdown wrapper here is pointless, because the
firmware immediately throws away the key anyway. Instead, refuse to do
anything if SNP has not been previously initialized.

This is an ABI break: before, this was a no-op and almost certainly a
mistake by userspace, and now it returns -ENODEV. ABI compatibility could be
maintained here by simply returning 0 in the check instead.
Published: 2026-07-25
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Linux kernel’s crypto:ccp subsystem prevents the SNP (Secure Nested Paging) feature from being properly initialized when the ioctl(SNP_VLEK_LOAD) call is used. The code would zero out the MSR_VM_HSAVE_PA register globally if SEV initialization fails while normal virtual machines are running, and then the next VMRUN attempt would trigger a general protection fault. This fault causes the host hypervisor to crash, resulting in a denial of service that brings down all virtual machines on the host. The weakness is an improper error handling path that effectively ignores a missing SNP initialization and then performs an operation that assumes a valid state, an error covered by CWE-909.

Affected Systems

All Linux kernel versions that include the generic crypto:ccp code path are impacted. The vulnerability exists in the core kernel and is therefore present in any distribution that has not incorporated the upstream patch. Since the code path is part of the syscall interface exposed via /dev/sev, the flaw affects any system that runs KVM with SEV support and does not have protective limits on access to the device.

Risk and Exploitability

The EPSS score is below 1% and the vulnerability does not appear in the CISA KEV catalog, indicating a low current exploitation probability. Nonetheless, the impact is severe enough to crash the host, so the CVSS score of 5.5 signals a moderate severity. An attacker would most likely need local or privileged userspace access to issue /dev/sev ioctl calls that trigger the faulty code path, such as SEV_PDH_GEN. Once triggered, the fault is almost guaranteed to occur on the next VMRUN, making the attack path reliable from the attacker’s perspective.

Generated by OpenCVE AI on August 5, 2026 at 00:49 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the ccp SNP initialization fix.
  • Restrict access to /dev/sev so that only trusted administrative users can issue SEV ioctls, and block untrusted processes from using the device.
  • If a patch cannot be applied immediately, consider disabling SNP or SEV support in the hypervisor configuration until the fix is available.

Generated by OpenCVE AI on August 5, 2026 at 00:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4724-1 linux-6.12 new package
History

Tue, 04 Aug 2026 15:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-405
CWE-547

Thu, 30 Jul 2026 04:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-405
CWE-547

Thu, 30 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-909
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) 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 SEV firmware docs for SNP_VLEK_LOAD note: > On SNP_SHUTDOWN, the VLEK is deleted. That is, the initialization/shutdown wrapper here is pointless, because the firmware immediately throws away the key anyway. Instead, refuse to do anything if SNP has not been previously initialized. This is an ABI break: before, this was a no-op and almost certainly a mistake by userspace, and now it returns -ENODEV. ABI compatibility could be maintained here by simply returning 0 in the check instead.
Title crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD)
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-25T08:49:41.411Z

Reserved: 2026-07-19T15:36:31.779Z

Link: CVE-2026-64308

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-25T10:17:11.917

Modified: 2026-08-11T15:00:57.447

Link: CVE-2026-64308

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64308 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T01:00:07Z

Weaknesses
  • CWE-909

    Missing Initialization of Resource