CVE-2026-43215
Awaiting Analysis Awaiting Analysis - Queue
Race Condition in Linux Kernel CIFS Module

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-06
Generated
2026-05-06
AI Q&A
2026-05-06
EPSS Evaluated
N/A
NVD
CVE-2026-43215
EUVD
EUVD-2026-27777
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel relates to improper locking usage in the CIFS (Common Internet File System) component, specifically for tcon (tree connection) fields.

Originally, a single lock called cifs_tcp_ses_lock was used to protect multiple objects, including server, session (ses), and tree connection (tcon) lists. Later, more granular locks (srv_lock, ses_lock, and tc_lock) were introduced to protect specific fields within their respective structures to avoid unnecessary serialization.

However, some uses of the old cifs_tcp_ses_lock remained for protecting tcon fields, which was incorrect. The vulnerability was fixed by replacing these remaining uses with the appropriate tc_lock, ensuring proper and granular locking.


How can this vulnerability impact me? :

Improper locking in kernel components like CIFS can lead to race conditions, data corruption, or system instability.

Because the vulnerability involved incorrect locking for tcon fields, it could potentially cause concurrency issues affecting file system operations over CIFS, possibly leading to crashes or data integrity problems.

Fixing the locking ensures more reliable and stable operation of CIFS in the Linux kernel.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart