CVE-2026-64309

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 4, 2026

Advisory Details (4)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a361c74bb12f3398c388905f1d325be642cd36e
generic

crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74768f73854d647a6462f252dc8782ab8a835211
generic

crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67ed191b4c8bdf432a3f32d1eb302880b4795cd1
generic

crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a1364da2f04217a36e2fdfa2db4ee025b383a20

Vendor Advisories for CVE-2026-64309(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 106 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 08:59 UTCEG score recompute
  3. 2026-09-18 08:59 UTCVendor advisory
  4. 2026-09-18 08:59 UTCGHSA enrichment
  5. 2026-09-17 09:13 UTCEG score recompute
  6. 2026-09-17 09:13 UTCVendor advisory
  7. 2026-09-17 09:13 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 06:35 UTCEG score recompute
  10. 2026-09-16 06:35 UTCVendor advisory
  11. 2026-09-16 06:35 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-14 15:54 UTCEG score recompute
  14. 2026-09-14 15:54 UTCVendor advisory
  15. 2026-09-14 15:54 UTCGHSA enrichment
  16. 2026-09-13 15:57 UTCVendor advisory
  17. 2026-09-13 15:57 UTCGHSA enrichment
  18. 2026-09-12 16:13 UTCEG score recompute
  19. 2026-09-12 16:13 UTCVendor advisory
  20. 2026-09-12 16:13 UTCGHSA enrichment
  21. 2026-09-11 16:28 UTCEG score recompute
  22. 2026-09-11 16:28 UTCVendor advisory
  23. 2026-09-11 16:28 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 09:37 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 13:29 UTCEG score recompute
  2. 2026-09-10 13:29 UTCVendor advisory
  3. 2026-09-10 13:29 UTCGHSA enrichment
  4. 2026-09-09 08:39 UTCEG score recompute
  5. 2026-09-09 08:39 UTCVendor advisory
  6. 2026-09-09 08:39 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:19 UTCEG score recompute
  9. 2026-09-07 21:19 UTCVendor advisory
  10. 2026-09-07 21:19 UTCGHSA enrichment
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 19:13 UTCEG score recompute
  13. 2026-09-06 19:13 UTCGHSA enrichment
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-05 19:21 UTCEG score recompute
  16. 2026-09-05 19:21 UTCGHSA enrichment
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 13:13 UTCEG score recompute 5.50
  19. 2026-09-04 13:13 UTCGHSA enrichment
  20. 2026-09-04 13:12 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 23:14 UTCGHSA enrichment
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 01:22 UTCEPSS rescore
  28. 2026-08-30 00:11 UTCGHSA enrichment
  29. 2026-08-28 21:42 UTCEPSS rescore
  30. 2026-08-26 14:47 UTCEPSS rescore
  31. 2026-08-26 00:38 UTCGHSA enrichment
  32. 2026-08-25 13:49 UTCEPSS rescore
  33. 2026-08-23 01:54 UTCGHSA enrichment
  34. 2026-08-23 00:19 UTCEPSS rescore
  35. 2026-08-21 23:49 UTCEPSS rescore
  36. 2026-08-20 22:55 UTCEPSS rescore
  37. 2026-08-20 03:38 UTCGHSA enrichment
  38. 2026-08-19 17:04 UTCEPSS rescore
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 05:25 UTCNVD update
  42. 2026-08-17 05:20 UTCGHSA enrichment
  43. 2026-08-17 05:05 UTCMITRE cvelistV5
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-15 01:30 UTCEPSS rescore
  46. 2026-08-14 13:26 UTCGHSA enrichment
  47. 2026-08-13 22:00 UTCEPSS rescore
  48. 2026-08-12 13:51 UTCEPSS rescore
  49. 2026-08-11 15:09 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-09 18:21 UTCGHSA enrichment
  52. 2026-08-09 13:47 UTCEPSS rescore
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-06 20:05 UTCGHSA enrichment
  55. 2026-08-06 13:47 UTCEPSS rescore
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:39 UTCEPSS rescore
  60. 2026-08-03 21:49 UTCGHSA enrichment
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-31 23:32 UTCEG score recompute
  65. 2026-07-31 23:32 UTCGHSA enrichment
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-29 01:12 UTCEG score recompute
  70. 2026-07-29 01:12 UTCGHSA enrichment
  71. 2026-07-28 15:37 UTCEPSS rescore
  72. 2026-07-27 14:14 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-26 02:52 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64309?
CVE-2026-64309 is a medium vulnerability published on July 25, 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., SEVPDHGEN) and…
When was CVE-2026-64309 disclosed?
CVE-2026-64309 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64309 actively exploited?
CVE-2026-64309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64309?
CVE-2026-64309 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64309, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64309

Explore →

Is Your Infrastructure Affected by CVE-2026-64309?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.