cifs: Fix locking usage for tcon fields
Summary
| CVE | CVE-2026-43215 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-06 12:16:41 UTC |
| Updated | 2026-05-06 13:07:51 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 953953abb66e52c224057ab91e404284fefeab62 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 601dd3b79769b38d30b693c40afdb2a4b7edf9d0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 8c59eeeeffa1524ef57e173a89a1a3ff539888d5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 96c4af418586ee9a6aab61738644366426e05316 git |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.128 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.75 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.16 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.6 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/8c59eeeeffa1524ef57e173a89a1a3ff539888d5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/953953abb66e52c224057ab91e404284fefeab62 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/601dd3b79769b38d30b693c40afdb2a4b7edf9d0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/96c4af418586ee9a6aab61738644366426e05316 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.