CVE-2026-64309
Last modified
CVE-2026-64309 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.22% 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_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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.12.75, < 6.12.96 |
| Linux | Linux Kernel | >= 6.16, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64309?
How severe is CVE-2026-64309?
How do I fix CVE-2026-64309?
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-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…7.8
- CVE-2026-64306In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64307In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64308In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6431The User Profile Builder – Beautiful User Registration Forms…7.2
- CVE-2026-64310In the Linux kernel, the following vulnerability has been re…5.5
- 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
- CVE-2026-64314In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64309?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
