CVE-2026-64309crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) 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 SNP_COMMIT command does not require the firmware to be in any particular state. Skip initializing it if it was previously uninitialized. The SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in Table 5 as a command that is allowed in the UNINIT state, but it is in fact allowed and a future documentation update will reflect that.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 – < 74768f73854d647a6462f252dc8782ab8a835211
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 7a361c74bb12f3398c388905f1d325be642cd36e
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 67ed191b4c8bdf432a3f32d1eb302880b4795cd1
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 5a1364da2f04217a36e2fdfa2db4ee025b383a20
- affected 6.12.75 – < 6.12.96
- affected 6.16
- unaffected < 6.16
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/74768f73854d647a6462f252dc8782ab8a835211 (opens in a new tab)
- https://git.kernel.org/stable/c/7a361c74bb12f3398c388905f1d325be642cd36e (opens in a new tab)
- https://git.kernel.org/stable/c/67ed191b4c8bdf432a3f32d1eb302880b4795cd1 (opens in a new tab)
- https://git.kernel.org/stable/c/5a1364da2f04217a36e2fdfa2db4ee025b383a20 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-49021 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64309)Record last updated .