CVE-2026-64307
Last modified
CVE-2026-64307 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7, < 345a6e869b33687e9268044bcaeeefd7c61da675; >= ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 441ea32cf2755a0dc593557056b00b7caa0651f5; >= ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 20f548cdac94860a164e5ebba4f7e4a01051cb06; >= ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 08f0e65e784c4b20e6e620dd4f68d8636073a3d2; >= 6.12.75, < 6.12.97 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64307?
How severe is CVE-2026-64307?
How do I fix CVE-2026-64307?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64301In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64302In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64303In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64304In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64305In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64306In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64308In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64309In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64310In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64311In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64312In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64313In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-64307?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
