CVE-2026-64598

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-06. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

smb/client: Fix error code in smb2_aead_req_alloc()

The "*num_sgs" variable is a u32 so "ERR_PTR(*num_sgs)" doesn't work. We would have to do something similar to the previous line where it's cast to int and then long. However, it's simpler to store the return in an int ret variable.

This bug would eventually result in a crash when dereference the invalid error pointer.

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

Published

August 6, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 8, 2026
No patch confirmed yet.
generic

smb/client: Fix error code in smb2_aead_req_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: Fix error code in smb2_aead_req_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: Fix error code in smb2_aead_req_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: Fix error code in smb2_aead_req_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: Fix error code in smb2_aead_req_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61f28012e5650c619223decdb7970e0d3162e949

Vendor Advisories for CVE-2026-64598(2)

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

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 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 30× in last 7d / 58× 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.

  1. 2026-08-21 00:53 UTCEG score recompute
  2. 2026-08-21 00:53 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 12:06 UTCGHSA enrichment
  5. 2026-08-19 23:16 UTCEG score recompute
  6. 2026-08-19 23:16 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:29 UTCGHSA enrichment
  9. 2026-08-18 21:42 UTCEG score recompute
  10. 2026-08-18 21:41 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 08:38 UTCGHSA enrichment
  13. 2026-08-17 19:26 UTCEG score recompute
  14. 2026-08-17 19:26 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 05:41 UTCEG score recompute
  17. 2026-08-17 05:41 UTCGHSA enrichment
  18. 2026-08-17 05:13 UTCEG score recompute
  19. 2026-08-17 05:13 UTCGHSA enrichment
  20. 2026-08-17 03:54 UTCGHSA enrichment
  21. 2026-08-16 15:07 UTCEG score recompute
  22. 2026-08-16 15:07 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:20 UTCEG score recompute
  25. 2026-08-16 02:20 UTCGHSA enrichment
Show 33 more
  1. 2026-08-15 13:34 UTCEG score recompute
  2. 2026-08-15 13:34 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:42 UTCGHSA enrichment
  5. 2026-08-14 11:55 UTCGHSA enrichment
  6. 2026-08-13 23:08 UTCEG score recompute
  7. 2026-08-13 23:08 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 10:21 UTCGHSA enrichment
  10. 2026-08-12 21:34 UTCEG score recompute
  11. 2026-08-12 21:34 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 08:47 UTCGHSA enrichment
  14. 2026-08-11 20:00 UTCEG score recompute
  15. 2026-08-11 20:00 UTCGHSA enrichment
  16. 2026-08-11 07:13 UTCEG score recompute
  17. 2026-08-11 07:13 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 18:26 UTCGHSA enrichment
  20. 2026-08-10 05:37 UTCGHSA enrichment
  21. 2026-08-09 16:51 UTCEG score recompute
  22. 2026-08-09 16:51 UTCGHSA enrichment
  23. 2026-08-09 13:47 UTCEPSS rescore
  24. 2026-08-09 04:04 UTCEG score recompute
  25. 2026-08-09 04:04 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 15:17 UTCEG score recompute 8.80
  28. 2026-08-08 15:17 UTCGHSA enrichment
  29. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 08:21 UTCNVD update
  32. 2026-08-06 07:25 UTCEG score recompute
  33. 2026-08-06 07:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64598?
CVE-2026-64598 is a high vulnerability published on August 6, 2026. In the Linux kernel, the following vulnerability has been resolved: smb/client: Fix error code in smb2aeadreq_alloc() The "num_sgs" variable is a u32 so "ERR_PTR(num_sgs)" doesn't work. We would have to do something similar to the previous line where it's cast to int and then long. However, it's…
When was CVE-2026-64598 disclosed?
CVE-2026-64598 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64598 actively exploited?
CVE-2026-64598 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 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64598?
CVE-2026-64598 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64598, 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-64598

Explore →

Is Your Infrastructure Affected by CVE-2026-64598?

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