CVE-2026-64136
Medium
Elevated severity or exploit probability.
CVSS base
9.8
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.5%
41.2th percentile
CISA KEV
Not listed
Weakness / dates
—
Published 2026-07-19 · modified 2026-08-13
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | N | Network |
| Attack Complexity | L | Low |
| Privileges Required | N | None |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-07-19 — Published (NVD)
- 2026-08-13 — Last modified (NVD)
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().
Affected
References
- https://git.kernel.org/stable/c/13fb413ae22a37c69341918a6d651d19a9b0b9b7
- https://git.kernel.org/stable/c/4d8690dace005a38e6dbde9ecce2da3ad85c7c41
- https://git.kernel.org/stable/c/7df1df6f40c0720d30206aa35c0343b962350e0d
- https://git.kernel.org/stable/c/bf4ebdb19ff9b3cdf992b50715fe61633327416a
- https://git.kernel.org/stable/c/e374f4e496fef8168784f93a4477d67be34485fd