crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (CVE-2026-64309) | HOL Guard CVE

Medium · CVSS 5.5CVE-2026-64309

crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)

Answer in brief

CVE-2026-64309 records a Medium severity (CVSS 5.5) 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.

Published Jul 25, 2026Updated Sep 4, 2026Source checked Oct 1, 2026First seen by HOL Aug 11, 2026Material review Sep 4, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.5
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 5.5. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:o:linux:linux_kernel::::::::	Not reported	Not reported

Mapped affected packages and fixed versions
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

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 74768f73854d647a6462f252dc8782ab8a835211 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.