Skip to content
Infrastructure

CVE-2026-43215

8.8
High
EPSS 0.30%Patch availableMay 8, 2026

Linux kernel CIFS locking fix; potential race in tcon fields

common questions

Is CVE-2026-43215 being exploited?

Not confirmed. CVE-2026-43215 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-43215?

CVE-2026-43215 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-43215?

Yes. A fix has been recorded for CVE-2026-43215. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43215 affect?

CVE-2026-43215 affects Linux kernel CIFS subsystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43215?

Update to patched kernel with CIFS locking fix

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel CIFS subsystem
impact

Race in CIFS tcon locking could crash kernel or enable local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and < 953953abb66e52c224057ab91e404284fefeab62
  • affected>= d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and < 601dd3b79769b38d30b693c40afdb2a4b7edf9d0
  • affected>= d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and < 3969db6b22e3d90d8c5f22ac1a7fe0350a94c136
  • affected>= d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and < 8c59eeeeffa1524ef57e173a89a1a3ff539888d5
  • affected>= d7d7a66aacd6fd8ca57baf08a7bac5421282f6f8 and < 96c4af418586ee9a6aab61738644366426e05316
  • affected6.0
vendor says fixed in< 6.0, >= 6.6.128 and <= 6.6.*, >= 6.12.75 and <= 6.12.*, >= 6.18.16 and <= 6.18.*, >= 6.19.6 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free