CVE-2026-31476

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 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: do not expire session on binding failure

When a multichannel session binding request fails (e.g. wrong password), the error path unconditionally sets sess->state = SMB2_SESSION_EXPIRED. However, during binding, sess points to the target session looked up via ksmbd_session_lookup_slowpath() -- which belongs to another connection's user. This allows a remote attacker to invalidate any active session by simply sending a binding request with a wrong password (DoS).

Fix this by skipping session expiration when the failed request was a binding attempt, since the session does not belong to the current connection. The reference taken by ksmbd_session_lookup_slowpath() is still correctly released via ksmbd_user_session_put().

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
39.4%
KEV
Not listed

Published

April 22, 2026

Last Modified

June 1, 2026

Advisory Details (6)

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: do not expire session on binding failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d1888b4a7aec518b707f6eca0bf08992c0e8da3

Vendor Advisories for CVE-2026-31476(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 161 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31476?
CVE-2026-31476 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: do not expire session on binding failure When a multichannel session binding request fails (e.g. wrong password), the error path unconditionally sets sess->state = SMB2SESSIONEXPIRED. However, during binding, sess points to…
When was CVE-2026-31476 disclosed?
CVE-2026-31476 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31476 actively exploited?
CVE-2026-31476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31476?
CVE-2026-31476 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-31476?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31476, 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

Explore the affected products and dependency analysis for CVE-2026-31476

Explore →

Is Your Infrastructure Affected by CVE-2026-31476?

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