cifs: Fix locking usage for tcon fields
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 · < 96c4af418586ee9a6aab61738644366426e05316| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cifs: Fix locking usage for tcon fields
We used to use the cifs_tcp_ses_lock to protect a lot of objects that are not just the server, ses or tcon lists. We later introduced srv_lock, ses_lock and tc_lock to protect fields within the corresponding structs. This was done to provide a more granular protection and avoid unnecessary serialization.
There were still a couple of uses of cifs_tcp_ses_lock to provide tcon fields. In this patch, I've replaced them with tc_lock.
From the CVE record · Linux
The Linux kernel's CIFS code used the wrong lock to protect some tcon fields, creating a potential race condition. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with CIFS support should check their deployments; affected versions are not specified.