CVE-2026-64136
Linux Kernel vulnerability
- Published19 Jul 2026
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().
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
- 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
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
Frequently asked
Is CVE-2026-64136 being actively exploited?
CVE-2026-64136 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.
How severe is CVE-2026-64136?
CVE-2026-64136 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.49% probability of exploitation.
Which products are affected by CVE-2026-64136?
Affected products include Linux Kernel.
How do I fix CVE-2026-64136?
Upgrade affected software to a fixed version, for example Linux Kernel 6.12.92 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-64136 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.