CVE-2026-64136

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

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

A fix is available — apply it.

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

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()

Commit 96c4af418586 ("cifs: Fix locking usage for tcon fields") refactored cifs code to change cifs_tcp_ses_lock for tc_lock around tc_count changes.

There was missing lock around tc_count increment inside smb2_find_smb_sess_tcon_unlocked().

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

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (5)

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

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d8690dace005a38e6dbde9ecce2da3ad85c7c41
generic

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13fb413ae22a37c69341918a6d651d19a9b0b9b7

Vendor Advisories for CVE-2026-64136(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-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-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-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

(2 across 2 ecosystems)
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 60× in last 7d / 352× 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 422 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64136?
CVE-2026-64136 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: protect tccount increment in smb2findsmbsesstconunlocked() Commit 96c4af418586 ("cifs: Fix locking usage for tcon fields") refactored cifs code to change cifstcpseslock for tclock around tc_count changes. There was…
When was CVE-2026-64136 disclosed?
CVE-2026-64136 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64136 actively exploited?
CVE-2026-64136 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 59.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64136?
CVE-2026-64136 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64136?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64136, 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-64136

Explore →

Is Your Infrastructure Affected by CVE-2026-64136?

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

Start Free Scan →Browse All CVEs