CVE-2026-31409

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: unset conn->binding on failed binding request

When a multichannel SMB2_SESSION_SETUP request with SMB2_SESSION_REQ_FLAG_BINDING fails ksmbd sets conn->binding = true but never clears it on the error path. This leaves the connection in a binding state where all subsequent ksmbd_session_lookup_all() calls fall back to the global sessions table. This fix it by clearing conn->binding = false in the error path.

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
38%
KEV
Not listed

Published

April 6, 2026

Last Modified

August 5, 2026

Advisory Details (6)

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

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d073870dab8f6dadced81d13d273ff0b21cb7f4e
generic

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9feb2d1bf86d9e5e66b8565f37f8d3a7d281a772
generic

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89afe5e2dbea6e9d8e5f11324149d06fa3a4efca
generic

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ebef4a220a1ebe345de899ebb9ae394206fe921
generic

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6260fc85ed1298a71d24a75d01f8b2e56d489a60
generic

ksmbd: unset conn->binding on failed binding request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/282343cf8a4a5a3603b1cb0e17a7083e4a593b03

Vendor Advisories for CVE-2026-31409(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.209osv

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
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 (122 versions)6.19.10-1

All Vendor Advisories

(24)

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

Frequently asked(5)

What is CVE-2026-31409?
CVE-2026-31409 is a high vulnerability published on April 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: unset conn->binding on failed binding request When a multichannel SMB2SESSIONSETUP request with SMB2SESSIONREQFLAGBINDING fails ksmbd sets conn->binding = true but never clears it on the error path. This leaves the…
When was CVE-2026-31409 disclosed?
CVE-2026-31409 was first published in the National Vulnerability Database on April 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-31409 actively exploited?
CVE-2026-31409 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 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31409?
CVE-2026-31409 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31409, 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-31409

Explore →

Is Your Infrastructure Affected by CVE-2026-31409?

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