Skip to main content
VulnerabilityPublished

CVE-2026-64136: Linux kernel · smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()

Source GCVE Database

0
Authoritative record:CVE-2026-64136· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical · fixed in e374f4e496fef8168784f93a4477d67be34485fd : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e374f4e496fef8168784f93a4477d67be34485fd, bf4ebdb19ff9b3cdf992b50715fe61633327416a, 13fb413ae22a37c69341918a6d651d19a9b0b9b7 +6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.6.128 <6.6.142
  • >=6.12.75 <6.12.92
  • >=6.18.16 <6.18.34
  • >=6.19.6 <6.20
Fixed in
  • e374f4e496fef8168784f93a4477d67be34485fd
  • bf4ebdb19ff9b3cdf992b50715fe61633327416a
  • 13fb413ae22a37c69341918a6d651d19a9b0b9b7
  • 7df1df6f40c0720d30206aa35c0343b962350e0d
  • 6.20
  • 6.18.34
  • 6.12.92
  • 6.6.142
  • 4d8690dace005a38e6dbde9ecce2da3ad85c7c41
LinuxLinuxAffected
  • =7.0
Fixed in–

AI-suggested

A fix has been committed to the Linux kernel source code (commit 96c4af418586) that properly protects the tc_count increment with locking. Users should apply the updated kernel version containing this fix once it is released. Patch status is not explicitly confirmed in the provided data; check the Linux kernel vendor advisory or source repository for the exact fixed versions and update accordingly.

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

References

Community reviews

Loading reviews…