CVE-2026-64136

CRITICALCVSS 9.8/10EPSS 0.49%

Last modified

CVE-2026-64136 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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().. EPSS estimates a 0.49% chance of exploitation in the next 30 days.

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

Metrics

CVSS 3.1
9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.49%

39.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 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
LinuxLinux7.0

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64136?
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().
How severe is CVE-2026-64136?
CVE-2026-64136 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.49% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64136?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64136?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST