CVE-2026-64136: Linux kernel · smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()
Source GCVE Database
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| 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
- nvd.nist.gov/vuln/detail/CVE-2026-64136 (opens in a new tab)
- git.kernel.org/stable/c/13fb413ae22a37c69341918a6d651d19a9b0b9b7 (opens in a new tab)
- git.kernel.org/stable/c/4d8690dace005a38e6dbde9ecce2da3ad85c7c41 (opens in a new tab)
- git.kernel.org/stable/c/7df1df6f40c0720d30206aa35c0343b962350e0d (opens in a new tab)
- git.kernel.org/stable/c/bf4ebdb19ff9b3cdf992b50715fe61633327416a (opens in a new tab)
- git.kernel.org/stable/c/e374f4e496fef8168784f93a4477d67be34485fd (opens in a new tab)