Nixpkgs security tracker
Dismissed
(max. allowed matches exceeded)
Permalink
CVE-2026-64136
9.8 CRITICAL
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()
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
Affected products
Linux
- ==7.0
- <6.6.142
- <e374f4e496fef8168784f93a4477d67be34485fd
- <7.0
- ==8c59eeeeffa1524ef57e173a89a1a3ff539888d5
- <4d8690dace005a38e6dbde9ecce2da3ad85c7c41
- =<6.18.*
- <bf4ebdb19ff9b3cdf992b50715fe61633327416a
- <6.18.34
- =<7.0.*
- =<6.12.*
- <6.12.92
- <7df1df6f40c0720d30206aa35c0343b962350e0d
- =<6.6.*
- <6.20
- =<*
- <13fb413ae22a37c69341918a6d651d19a9b0b9b7