5.5

CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG)

Analyzed
AliasesUBUNTU-CVE-2026-64307DEBIAN-CVE-2026-64307
Published 25-07-2026Last modified 17-08-2026

Vulnerability summary

CVE-2026-64307 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 6.2% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.17%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 17 · Related 17

Timeline

  1. 25-07-2026
    PublishedVulnerability first disclosed.
  2. 17-08-2026
    Last modifiedVulnerability information updated.

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

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.17%

Chance of exploitation in the next 30 days

Percentile

6%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.17% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu119 products
  • linux< 7.0.0-31.31
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 7.0.0-1012.12
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.12.100-1 | < 7.1.4-1
  • linux-6.12< 6.12.100-1~deb12u1
Linux2 products
  • linux≥ 1c3506ea8599a3ad1b9aae5cbd573134f8d18db7, < 345a6e869b33687e9268044bcaeeefd7c61da675 | ≥ ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 441ea32cf2755a0dc593557056b00b7caa0651f5 | ≥ ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 20f548cdac94860a164e5ebba4f7e4a01051cb06 | ≥ ceac7fb89e8da465aec3ac3c20477f912f5c3a6c, < 08f0e65e784c4b20e6e620dd4f68d8636073a3d2 | ≥ 6.12.75, < 6.12.97 | 6.16
  • linux_kernel≥ 6.12.75, < 6.12.97 | ≥ 6.16, < 6.18.39 | ≥ 6.19, < 7.1.4

3 vendors · 123 products

References

19 links
Show all 19 references