CVE-2026-31717

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Elevated
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: Elevated riskExposed: 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: validate owner of durable handle on reconnect

Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to hijack an orphaned durable handle by predicting or brute-forcing the persistent ID.

According to MS-SMB2, the server MUST verify that the SecurityContext of the reconnect request matches the SecurityContext associated with the existing open. Add a durable_owner structure to ksmbd_file to store the original opener's UID, GID, and account name. and catpure the owner information when a file handle becomes orphaned. and implementing ksmbd_vfs_compare_durable_owner() to validate the identity of the requester during SMB2_CREATE (DHnC).

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
60(Track)
EG Risk 60/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%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

ksmbd: validate owner of durable handle on reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: validate owner of durable handle on reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49110a8ce654bbe56bef7c5e44cce31f4b102b8a
generic

ksmbd: validate owner of durable handle on reconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00ce8d6789dae72d042a4522264964c72891ca37

Vendor Advisories for CVE-2026-31717(2)

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 @ 6.6.142—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.1-1~exp1 (129 versions)7.0.3-1—

All Vendor Advisories

(5)

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 8× in last 7d / 76× 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 244 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCTurtleARM/CVE-2026-31717-KSMBD-Exploit
    First seen May 4, 2026
    Open source ↗
  • GitHub PoCTurtleARM/ksmbrace
    First seen May 4, 2026

    ksmbd CVEs: CVE-2026-31717, CVE-2026-68083

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-31717?
CVE-2026-31717 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate owner of durable handle on reconnect Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to…
When was CVE-2026-31717 disclosed?
CVE-2026-31717 was first published in the National Vulnerability Database on May 1, 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-31717 actively exploited?
CVE-2026-31717 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 63.4% of all scored CVEs.
What is the CVSS score of CVE-2026-31717?
CVE-2026-31717 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31717, 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-31717

Explore →

Is Your Infrastructure Affected by CVE-2026-31717?

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

Start Free Scan →Browse All CVEs