smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 96c4af418586ee9a6aab61738644366426e05316 · < 4d8690dace005a38e6dbde9ecce2da3ad85c7c41| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel SMB client has a missing lock around a tc_count increment in smb2_find_smb_sess_tcon_unlocked(). This creates a race condition; the input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.