Answer in brief
CVE-2026-64136 records a Unknown severity vulnerability in smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=953953abb66e52c224057ab91e404284fefeab62 <7df1df6f40c0720d30206aa35c0343b962350e0d || >=601dd3b79769b38d30b693c40afdb2a4b7edf9d0 <13fb413ae22a37c69341918a6d651d19a9b0b9b7 || >=3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 <bf4ebdb19ff9b3cdf992b50715fe61633327416a || >=96c4af418586ee9a6aab61738644366426e05316 <e374f4e496fef8168784f93a4477d67be34485fd || >=96c4af418586ee9a6aab61738644366426e05316 <4d8690dace005a38e6dbde9ecce2da3ad85c7c41 || 8c59eeeeffa1524ef57e173a89a1a3ff539888d5 || >=6.6.128 <6.6.142 || >=6.12.75 <6.12.92 || >=6.18.16 <6.18.34 || >=6.19.6 <6.20 | 7df1df6f40c0720d30206aa35c0343b962350e0d, 13fb413ae22a37c69341918a6d651d19a9b0b9b7, bf4ebdb19ff9b3cdf992b50715fe61633327416a, e374f4e496fef8168784f93a4477d67be34485fd, 4d8690dace005a38e6dbde9ecce2da3ad85c7c41, 6.6.142, 6.12.92, 6.18.34, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64136 records a Unknown severity vulnerability in smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=953953abb66e52c224057ab91e404284fefeab62 <7df1df6f40c0720d30206aa35c0343b962350e0d || >=601dd3b79769b38d30b693c40afdb2a4b7edf9d0 <13fb413ae22a37c69341918a6d651d19a9b0b9b7 || >=3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 <bf4ebdb19ff9b3cdf992b50715fe61633327416a || >=96c4af418586ee9a6aab61738644366426e05316 <e374f4e496fef8168784f93a4477d67be34485fd || >=96c4af418586ee9a6aab61738644366426e05316 <4d8690dace005a38e6dbde9ecce2da3ad85c7c41 || 8c59eeeeffa1524ef57e173a89a1a3ff539888d5 || >=6.6.128 <6.6.142 || >=6.12.75 <6.12.92 || >=6.18.16 <6.18.34 || >=6.19.6 <6.20 | 7df1df6f40c0720d30206aa35c0343b962350e0d, 13fb413ae22a37c69341918a6d651d19a9b0b9b7, bf4ebdb19ff9b3cdf992b50715fe61633327416a, e374f4e496fef8168784f93a4477d67be34485fd, 4d8690dace005a38e6dbde9ecce2da3ad85c7c41, 6.6.142, 6.12.92, 6.18.34, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.