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
41%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (5)

Auto-updated Sep 17, 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(3)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-09-18ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.45.1.el9_82026-09-08redhat
redhatkernel-0:6.12.0-211.50.1.el10_22026-09-01redhat

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 (141 versions)7.0.12-1—

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 40× in last 7d / 188× 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 511 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 58.8% 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