crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG)
Summary
| CVE | CVE-2026-64307 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-25 10:17:11 UTC |
| Updated | 2026-07-25 10:17:11 UTC |
| 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 |
Risk And Classification
EPSS: 0.002150000 probability, percentile 0.121210000 (date 2026-07-28)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 345a6e869b33687e9268044bcaeeefd7c61da675 git | Not specified |
| CNA | Linux | Linux | affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 441ea32cf2755a0dc593557056b00b7caa0651f5 git | Not specified |
| CNA | Linux | Linux | affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 20f548cdac94860a164e5ebba4f7e4a01051cb06 git | Not specified |
| CNA | Linux | Linux | affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 08f0e65e784c4b20e6e620dd4f68d8636073a3d2 git | Not specified |
| CNA | Linux | Linux | affected 6.12.75 6.12.97 semver | Not specified |
| CNA | Linux | Linux | affected 6.16 | Not specified |
| CNA | Linux | Linux | unaffected 6.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.97 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.39 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.4 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/345a6e869b33687e9268044bcaeeefd7c61da675 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/20f548cdac94860a164e5ebba4f7e4a01051cb06 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/441ea32cf2755a0dc593557056b00b7caa0651f5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/08f0e65e784c4b20e6e620dd4f68d8636073a3d2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.