CVE-2026-43215
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Modified
Affected
- Linux Kernel < 6.6.128
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43215.md and follow it. Check whether this project is affected by CVE-2026-43215. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3969db6b22e3d90d8c5f22ac1a7fe0350a94c136
- https://git.kernel.org/stable/c/601dd3b79769b38d30b693c40afdb2a4b7edf9d0
- https://git.kernel.org/stable/c/8c59eeeeffa1524ef57e173a89a1a3ff539888d5
- https://git.kernel.org/stable/c/953953abb66e52c224057ab91e404284fefeab62
- https://git.kernel.org/stable/c/96c4af418586ee9a6aab61738644366426e05316
References
- https://git.kernel.org/stable/c/3969db6b22e3d90d8c5f22ac1a7fe0350a94c136
- https://git.kernel.org/stable/c/601dd3b79769b38d30b693c40afdb2a4b7edf9d0
- https://git.kernel.org/stable/c/8c59eeeeffa1524ef57e173a89a1a3ff539888d5
- https://git.kernel.org/stable/c/92d197ef7e9bb4994dae2bb17c2f19fa09d219a2
- https://git.kernel.org/stable/c/953953abb66e52c224057ab91e404284fefeab62
- https://git.kernel.org/stable/c/96c4af418586ee9a6aab61738644366426e05316