CVE-2026-64307crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG)
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% 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_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
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 94% of all CVEs (12 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 – < 345a6e869b33687e9268044bcaeeefd7c61da675
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 441ea32cf2755a0dc593557056b00b7caa0651f5
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 20f548cdac94860a164e5ebba4f7e4a01051cb06
- affected ceac7fb89e8da465aec3ac3c20477f912f5c3a6c – < 08f0e65e784c4b20e6e620dd4f68d8636073a3d2
- affected 6.12.75 – < 6.12.97
- affected 6.16
- unaffected < 6.16
- unaffected 6.12.97 – ≤ 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/345a6e869b33687e9268044bcaeeefd7c61da675 (opens in a new tab)
- https://git.kernel.org/stable/c/441ea32cf2755a0dc593557056b00b7caa0651f5 (opens in a new tab)
- https://git.kernel.org/stable/c/20f548cdac94860a164e5ebba4f7e4a01051cb06 (opens in a new tab)
- https://git.kernel.org/stable/c/08f0e65e784c4b20e6e620dd4f68d8636073a3d2 (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-49019 (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-64307)Record last updated .