Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31717ksmbd: validate owner of durable handle on reconnect

Description

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).

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31717, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.44% · top 61% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 8df4bcdb0a4232192b2445256c39b787d58ef14d – < 712cdf917e77a6444ce3836874829d770db20ee6
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < 00ce8d6789dae72d042a4522264964c72891ca37
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < c908c853f304a4969b5aa10eba0b50350cc65b80
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < 49110a8ce654bbe56bef7c5e44cce31f4b102b8a
    • affected 6.6.32 – < 6.6.142
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.25 – ≤ 6.18.*
    • unaffected 7.0.2 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31717 badge
[![CVE-2026-31717](https://cveledger.app/badge/CVE-2026-31717.svg)](https://cveledger.app/cve/CVE-2026-31717)

Record last updated .