Answer in brief
CVE-2026-64309 records a Unknown severity vulnerability in crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 <74768f73854d647a6462f252dc8782ab8a835211 || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <7a361c74bb12f3398c388905f1d325be642cd36e || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <67ed191b4c8bdf432a3f32d1eb302880b4795cd1 || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <5a1364da2f04217a36e2fdfa2db4ee025b383a20 || >=6.12.75 <6.12.96 | 74768f73854d647a6462f252dc8782ab8a835211, 7a361c74bb12f3398c388905f1d325be642cd36e, 67ed191b4c8bdf432a3f32d1eb302880b4795cd1, 5a1364da2f04217a36e2fdfa2db4ee025b383a20, 6.12.96 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64309 records a Unknown severity vulnerability in crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1c3506ea8599a3ad1b9aae5cbd573134f8d18db7 <74768f73854d647a6462f252dc8782ab8a835211 || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <7a361c74bb12f3398c388905f1d325be642cd36e || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <67ed191b4c8bdf432a3f32d1eb302880b4795cd1 || >=ceac7fb89e8da465aec3ac3c20477f912f5c3a6c <5a1364da2f04217a36e2fdfa2db4ee025b383a20 || >=6.12.75 <6.12.96 | 74768f73854d647a6462f252dc8782ab8a835211, 7a361c74bb12f3398c388905f1d325be642cd36e, 67ed191b4c8bdf432a3f32d1eb302880b4795cd1, 5a1364da2f04217a36e2fdfa2db4ee025b383a20, 6.12.96 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.