CVE-2026-43215
HIGHDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 33% of all known CVEs.
References
Related Vulnerabilities
Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-10072 | High | 7.5 | 73% | - | Fix |
| CVE-2002-1850 | High | 7.5 | 17% | - | Fix |
| CVE-2009-2699 | High | 7.5 | 14% | - | Fix |
| CVE-2004-0174 | High | 7.5 | 12% | - | - |
| CVE-2009-4272 | High | 7.5 | 11% | - | - |
| CVE-2020-24606 | High | 8.6 | 5.0% | - | Fix |
Common questions
How do I fix CVE-2026-43215?
Published advisories record a fix for 159 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-43215 being actively exploited?
Not that we know of. CVE-2026-43215 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 33% of all scored CVEs.
How severe is CVE-2026-43215?
CVE-2026-43215 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-43215 affect?
Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-6.8 (Ubuntu), and 155 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-43215
Markdown
[](https://tridentstack.com/cve/CVE-2026-43215)HTML
<a href="https://tridentstack.com/cve/CVE-2026-43215"><img src="https://tridentstack.com/cve/badge/CVE-2026-43215.svg" alt="CVE-2026-43215"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-11.