CVE-2026-43215: cifs: Fix locking usage for tcon fields
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136, 601dd3b79769b38d30b693c40afdb2a4b7edf9d0, 8c59eeeeffa1524ef57e173a89a1a3ff539888d5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136, 601dd3b79769b38d30b693c40afdb2a4b7edf9d0, 8c59eeeeffa1524ef57e173a89a1a3ff539888d5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 6, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-667
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 92d197ef7e9bb4994dae2bb17c2f19fa09d219a2affected · git
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 953953abb66e52c224057ab91e404284fefeab62affected · git
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 601dd3b79769b38d30b693c40afdb2a4b7edf9d0affected · git
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136affected · git
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 8c59eeeeffa1524ef57e173a89a1a3ff539888d5affected · git
- d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and later · before 96c4af418586ee9a6aab61738644366426e05316affected · git
- before 6.0not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.128 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43213May 6, 2026 · wifi: rtw89: pci: validate sequence number of TX release report30Monitor
- ← EarlierCVE-2026-43214May 6, 2026 · KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()31Monitor
- Later →CVE-2026-43216May 6, 2026 · net: Drop the lock in skb_may_tx_timestamp()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136 | Vendor (CNA) |
| Linux Linux | 601dd3b79769b38d30b693c40afdb2a4b7edf9d0 | Vendor (CNA) |
| Linux Linux | 8c59eeeeffa1524ef57e173a89a1a3ff539888d5 | Vendor (CNA) |
| Linux Linux | 92d197ef7e9bb4994dae2bb17c2f19fa09d219a2 | Vendor (CNA) |
| Linux Linux | 953953abb66e52c224057ab91e404284fefeab62 | Vendor (CNA) |
| Linux Linux | 96c4af418586ee9a6aab61738644366426e05316 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0196 · May 8, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/601dd3b79769b38d30b693c40afdb2a4b7edf9d0
- git.kernel.org/stable/c/8c59eeeeffa1524ef57e173a89a1a3ff539888d5
- git.kernel.org/stable/c/92d197ef7e9bb4994dae2bb17c2f19fa09d219a2
- git.kernel.org/stable/c/953953abb66e52c224057ab91e404284fefeab62
- git.kernel.org/stable/c/96c4af418586ee9a6aab61738644366426e05316
Vendor advisories and official records. Exploit/PoC links are deliberately left out.