Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64136

smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64136, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.41% · top 65% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 92d197ef7e9bb4994dae2bb17c2f19fa09d219a2 – < 7585d4242f59185b084957fa077396e53dbf7c24
    • affected 953953abb66e52c224057ab91e404284fefeab62 – < 7df1df6f40c0720d30206aa35c0343b962350e0d
    • affected 601dd3b79769b38d30b693c40afdb2a4b7edf9d0 – < 13fb413ae22a37c69341918a6d651d19a9b0b9b7
    • affected 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 – < bf4ebdb19ff9b3cdf992b50715fe61633327416a
    • affected 96c4af418586ee9a6aab61738644366426e05316 – < e374f4e496fef8168784f93a4477d67be34485fd
    • affected 96c4af418586ee9a6aab61738644366426e05316 – < 4d8690dace005a38e6dbde9ecce2da3ad85c7c41
    • affected 8c59eeeeffa1524ef57e173a89a1a3ff539888d5
    • affected 6.6.128 – < 6.6.142
    • affected 6.12.75 – < 6.12.92
    • affected 6.18.16 – < 6.18.34
    • affected 6.19.6 – < 6.20
  • Linux · Linux

    • affected 7.0
    • unaffected < 7.0
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64136 badge
[![CVE-2026-64136](https://cveledger.app/badge/CVE-2026-64136.svg)](https://cveledger.app/cve/CVE-2026-64136)

Record last updated .