CVE-2026-64005

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/smc: Do not re-initialize smc hashtables

INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) are called after smc_nl_init(), proto_register() and sock_register(). This can lead to smc_v*_hashinfo.ht being reset even though hash entries already exist and are being used, possibly resulting in a corrupted list.

Remove unnecessary and dangerous re-initialisation of smc_v*_hashinfo.ht in smc_init(); it is implicitly initialised to zero anyhow. Add HLIST_HEAD_INIT to the definitions for clarity.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
generic

net/smc: Do not re-initialize smc hashtables - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d

Vendor Advisories for CVE-2026-64005(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

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 33× in last 7d / 162× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64005?
CVE-2026-64005 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net/smc: Do not re-initialize smc hashtables INITHLISTHEAD(&smcv*hashinfo.ht) are called after smcnlinit(), protoregister() and sockregister(). This can lead to smcv*hashinfo.ht being reset even though hash entries already exist…
When was CVE-2026-64005 disclosed?
CVE-2026-64005 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64005 actively exploited?
CVE-2026-64005 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64005?
CVE-2026-64005 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64005, 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-64005

Explore →

Is Your Infrastructure Affected by CVE-2026-64005?

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

Start Free Scan →Browse All CVEs