{"api_version":"1","generated_at":"2026-07-26T00:29:03+00:00","cve":"CVE-2026-64309","urls":{"html":"https://cve.report/CVE-2026-64309","api":"https://cve.report/api/cve/CVE-2026-64309.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64309","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64309"},"summary":{"title":"crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)\n\nSashiko notes:\n\n> if SEV initialization fails and KVM is actively running normal VMs, could a\n> userspace process trigger this code path via /dev/sev ioctls (e.g.,\n> SEV_PDH_GEN) and zero out MSR_VM_HSAVE_PA globally? Would the next VMRUN\n> execution for an active VM trigger a general protection fault and crash the\n> host?\n\nThe SNP_COMMIT command does not require the firmware to be in any\nparticular state. Skip initializing it if it was previously uninitialized.\n\nThe SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in\nTable 5 as a command that is allowed in the UNINIT state, but it is in fact\nallowed and a future documentation update will reflect that.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:12","updated_at":"2026-07-25 10:17:12"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/74768f73854d647a6462f252dc8782ab8a835211","name":"https://git.kernel.org/stable/c/74768f73854d647a6462f252dc8782ab8a835211","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/67ed191b4c8bdf432a3f32d1eb302880b4795cd1","name":"https://git.kernel.org/stable/c/67ed191b4c8bdf432a3f32d1eb302880b4795cd1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5a1364da2f04217a36e2fdfa2db4ee025b383a20","name":"https://git.kernel.org/stable/c/5a1364da2f04217a36e2fdfa2db4ee025b383a20","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7a361c74bb12f3398c388905f1d325be642cd36e","name":"https://git.kernel.org/stable/c/7a361c74bb12f3398c388905f1d325be642cd36e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64309","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64309","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 74768f73854d647a6462f252dc8782ab8a835211 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 7a361c74bb12f3398c388905f1d325be642cd36e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 67ed191b4c8bdf432a3f32d1eb302880b4795cd1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c 5a1364da2f04217a36e2fdfa2db4ee025b383a20 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12.75 6.12.96 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.96 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.39 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64309","cve":"CVE-2026-64309","epss":"0.002250000","percentile":"0.132610000","score_date":"2026-07-25","updated_at":"2026-07-26 00:12:33"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/crypto/ccp/sev-dev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"74768f73854d647a6462f252dc8782ab8a835211","status":"affected","version":"1c3506ea8599a3ad1b9aae5cbd573134f8d18db7","versionType":"git"},{"lessThan":"7a361c74bb12f3398c388905f1d325be642cd36e","status":"affected","version":"ceac7fb89e8da465aec3ac3c20477f912f5c3a6c","versionType":"git"},{"lessThan":"67ed191b4c8bdf432a3f32d1eb302880b4795cd1","status":"affected","version":"ceac7fb89e8da465aec3ac3c20477f912f5c3a6c","versionType":"git"},{"lessThan":"5a1364da2f04217a36e2fdfa2db4ee025b383a20","status":"affected","version":"ceac7fb89e8da465aec3ac3c20477f912f5c3a6c","versionType":"git"},{"lessThan":"6.12.96","status":"affected","version":"6.12.75","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/crypto/ccp/sev-dev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.96","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.39","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.96","versionStartIncluding":"6.12.75","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.39","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)\n\nSashiko notes:\n\n> if SEV initialization fails and KVM is actively running normal VMs, could a\n> userspace process trigger this code path via /dev/sev ioctls (e.g.,\n> SEV_PDH_GEN) and zero out MSR_VM_HSAVE_PA globally? Would the next VMRUN\n> execution for an active VM trigger a general protection fault and crash the\n> host?\n\nThe SNP_COMMIT command does not require the firmware to be in any\nparticular state. Skip initializing it if it was previously uninitialized.\n\nThe SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in\nTable 5 as a command that is allowed in the UNINIT state, but it is in fact\nallowed and a future documentation update will reflect that."}],"providerMetadata":{"dateUpdated":"2026-07-25T08:49:42.035Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/74768f73854d647a6462f252dc8782ab8a835211"},{"url":"https://git.kernel.org/stable/c/7a361c74bb12f3398c388905f1d325be642cd36e"},{"url":"https://git.kernel.org/stable/c/67ed191b4c8bdf432a3f32d1eb302880b4795cd1"},{"url":"https://git.kernel.org/stable/c/5a1364da2f04217a36e2fdfa2db4ee025b383a20"}],"title":"crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64309","datePublished":"2026-07-25T08:49:42.035Z","dateReserved":"2026-07-19T15:36:31.779Z","dateUpdated":"2026-07-25T08:49:42.035Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:12","lastModifiedDate":"2026-07-25 10:17:12","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64309","Ordinal":"1","Title":"crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)","CVE":"CVE-2026-64309","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64309","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)\n\nSashiko notes:\n\n> if SEV initialization fails and KVM is actively running normal VMs, could a\n> userspace process trigger this code path via /dev/sev ioctls (e.g.,\n> SEV_PDH_GEN) and zero out MSR_VM_HSAVE_PA globally? Would the next VMRUN\n> execution for an active VM trigger a general protection fault and crash the\n> host?\n\nThe SNP_COMMIT command does not require the firmware to be in any\nparticular state. Skip initializing it if it was previously uninitialized.\n\nThe SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in\nTable 5 as a command that is allowed in the UNINIT state, but it is in fact\nallowed and a future documentation update will reflect that.","Type":"Description","Title":"crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)"}]}}}