CVE-2026-43215

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

cifs: Fix locking usage for tcon fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96c4af418586ee9a6aab61738644366426e05316
generic

cifs: Fix locking usage for tcon fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/953953abb66e52c224057ab91e404284fefeab62
generic

cifs: Fix locking usage for tcon fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c59eeeeffa1524ef57e173a89a1a3ff539888d5
generic

cifs: Fix locking usage for tcon fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/601dd3b79769b38d30b693c40afdb2a4b7edf9d0
generic

cifs: Fix locking usage for tcon fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3969db6b22e3d90d8c5f22ac1a7fe0350a94c136

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1055.56~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.128—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 215 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 16:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 20:01 UTCEG score recompute
  20. 2026-08-23 20:01 UTCVendor advisory
  21. 2026-08-23 20:00 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 12:55 UTCEG score recompute
  4. 2026-08-17 12:55 UTCVendor advisory
  5. 2026-08-17 12:55 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 04:53 UTCEG score recompute
  8. 2026-08-16 04:53 UTCVendor advisory
  9. 2026-08-16 04:53 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 15:27 UTCVendor advisory
  13. 2026-08-14 15:27 UTCGHSA enrichment
  14. 2026-08-14 03:27 UTCEG score recompute
  15. 2026-08-14 03:27 UTCVendor advisory
  16. 2026-08-14 03:27 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 06:07 UTCVendor advisory
  19. 2026-08-13 06:07 UTCGHSA enrichment
  20. 2026-08-12 17:00 UTCEG score recompute
  21. 2026-08-12 17:00 UTCVendor advisory
  22. 2026-08-12 17:00 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 16:00 UTCEG score recompute
  25. 2026-08-11 16:00 UTCVendor advisory
  26. 2026-08-11 16:00 UTCGHSA enrichment
  27. 2026-08-11 13:43 UTCEPSS rescore
  28. 2026-08-11 01:31 UTCEG score recompute
  29. 2026-08-11 01:31 UTCVendor advisory
  30. 2026-08-11 01:31 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 02:34 UTCVendor advisory
  33. 2026-08-10 02:34 UTCGHSA enrichment
  34. 2026-08-09 14:34 UTCEG score recompute
  35. 2026-08-09 14:34 UTCVendor advisory
  36. 2026-08-09 14:34 UTCGHSA enrichment
  37. 2026-08-09 13:46 UTCEPSS rescore
  38. 2026-08-09 02:35 UTCEG score recompute
  39. 2026-08-09 02:35 UTCVendor advisory
  40. 2026-08-09 02:35 UTCGHSA enrichment
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 10:57 UTCVendor advisory
  43. 2026-08-08 10:57 UTCGHSA enrichment
  44. 2026-08-07 22:56 UTCEG score recompute
  45. 2026-08-07 22:56 UTCVendor advisory
  46. 2026-08-07 22:56 UTCGHSA enrichment
  47. 2026-08-07 10:57 UTCVendor advisory
  48. 2026-08-07 10:57 UTCGHSA enrichment
  49. 2026-08-06 16:54 UTCEG score recompute
  50. 2026-08-06 16:54 UTCVendor advisory
  51. 2026-08-06 16:54 UTCGHSA enrichment
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 01:51 UTCEG score recompute
  54. 2026-08-06 01:51 UTCVendor advisory
  55. 2026-08-06 01:51 UTCGHSA enrichment
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 13:51 UTCEG score recompute
  58. 2026-08-05 13:51 UTCVendor advisory
  59. 2026-08-05 13:51 UTCGHSA enrichment
  60. 2026-08-04 15:10 UTCEPSS rescore
  61. 2026-08-04 10:38 UTCEPSS rescore
  62. 2026-08-03 19:52 UTCEG score recompute
  63. 2026-08-03 19:52 UTCVendor advisory
  64. 2026-08-03 19:52 UTCGHSA enrichment
  65. 2026-08-03 10:36 UTCEPSS rescore
  66. 2026-08-02 17:07 UTCVendor advisory
  67. 2026-08-02 17:07 UTCGHSA enrichment
  68. 2026-08-02 05:07 UTCEG score recompute
  69. 2026-08-02 05:07 UTCVendor advisory
  70. 2026-08-02 05:07 UTCGHSA enrichment
  71. 2026-08-02 02:27 UTCEPSS rescore
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-28 15:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43215?
CVE-2026-43215 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: cifs: Fix locking usage for tcon fields We used to use the cifstcpses_lock to protect a lot of objects that are not just the server, ses or tcon lists. We later introduced srvlock, seslock and tc_lock to protect fields within the…
When was CVE-2026-43215 disclosed?
CVE-2026-43215 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43215 actively exploited?
CVE-2026-43215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.6% of all scored CVEs.
What is the CVSS score of CVE-2026-43215?
CVE-2026-43215 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43215

Explore →

Is Your Infrastructure Affected by CVE-2026-43215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs