Description
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
Published: 2026-07-25
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel, the CCP crypto module fails to initialise the Intel SEV SNP feature during the ioctl(SNP_CONFIG) call, which can still be invoked by userspace. The call can zero the global MSR_VM_HSAVE_PA register; on the next VM run the host attempts to use the cleared register and triggers a general protection fault, causing a kernel panic. The flaw represents a denial‑of‑service weakness (CWE‑455).

Affected Systems

Any system running a Linux kernel that includes the CCP module and a loaded KVM subsystem may be affected. Specific version information is not available in the entry, so all kernel releases containing the CCP SNP code prior to the fix should be considered vulnerable.

Risk and Exploitability

The EPSS score is below 1% and the vulnerability is not listed in the CISA KEV catalog, indicating a low likelihood of widespread exploitation. However, the impact if exploited is severe, as the host crashes. Attackers would need access to the /dev/sev device and the ability to issue ioctl requests—typically requiring elevated privileges—but a local user could trigger the failure by invoking standard SEV ioctls such as SEV_PDH_GEN after SEV initialization has failed. The simplest exploit path involves calling ioctl(SNP_CONFIG) again after a failed initialization while KVM is loaded to zero the register and crash on the next VMRUN.

Generated by OpenCVE AI on August 3, 2026 at 19:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update to the latest Linux kernel release that includes the CCP SNP initialization fix (e.g., commit 08f0e65e7 or later).
  • If an immediate kernel upgrade is not possible, restrict access to the /dev/sev device by setting its permissions so that only the root user or a trusted system service can perform SEV ioctls, thereby preventing unprivileged processes from triggering the vulnerable code path.
  • Ensure the KVM module is not loaded or virtual machines are not started while SEV initialization has failed; if necessary, unload the kvm module or delay VM launch until SEV initialization succeeds.

Generated by OpenCVE AI on August 3, 2026 at 19:21 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
Debian DSA Debian DSA DSA-6405-1 linux security update
History

Sun, 02 Aug 2026 13:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20

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

Type Values Removed Values Added
Weaknesses CWE-455
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


Sun, 26 Jul 2026 02:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20

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_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
Title crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG)
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:40.782Z

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

Link: CVE-2026-64307

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

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

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

Link: CVE-2026-64307

cve-icon Redhat

Severity : Moderate

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

Links: CVE-2026-64307 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T19:30:04Z

Weaknesses
  • CWE-455

    Non-exit on Failed Initialization