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-31718ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger When a durable file handle survives session disconnect (TCP close without SMB2_LOGOFF), session_fd_check() sets fp->conn = NULL to preserve the handle for later reconnection. However, it did not clean up the byte-range locks on fp->lock_list. Later, when the durable scavenger thread times out and calls __ksmbd_close_fd(NULL, fp), the lock cleanup loop did: spin_lock(&fp->conn->llist_lock); This caused a slab use-after-free because fp->conn was NULL and the original connection object had already been freed by ksmbd_tcp_disconnect(). The root cause is asymmetric cleanup: lock entries (smb_lock->clist) were left dangling on the freed conn->lock_list while fp->conn was nulled out. To fix this issue properly, we need to handle the lifetime of smb_lock->clist across three paths: - Safely skip clist deletion when list is empty and fp->conn is NULL. - Remove the lock from the old connection's lock_list in session_fd_check() - Re-add the lock to the new connection's lock_list in ksmbd_reopen_durable_fd().

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-31718, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.36% · top 70% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 8df4bcdb0a4232192b2445256c39b787d58ef14d – < 0000a7780e0e446a28a273572f6ea8f7f582f694
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < e33c65f011980b4ad4abfd93585ec2079856368f
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < 3d6682726c2d3a46d31dae88b8166786b09b03ad
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < b34fc42cfe922e551f7a27d3ac3bb016e41d7dd9
    • affected c8efcc786146a951091588e5fa7e3c754850cb3c – < 235e32320a470fcd3998fb3774f2290a0eb302a1
    • affected 6.6.32 – < 6.6.140
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.84 – ≤ 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-31718 badge
[![CVE-2026-31718](https://cveledger.app/badge/CVE-2026-31718.svg)](https://cveledger.app/cve/CVE-2026-31718)

Record last updated .