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-64390ksmbd: track the connection owning a byte-range lock

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: track the connection owning a byte-range lock SMB2_LOCK adds each granted byte-range lock to both the file lock list and the lock list of the connection which handled the request. The final close and durable handle paths, however, remove the connection list entry while holding fp->conn->llist_lock. With SMB3 multichannel, the connection handling the LOCK request can be different from the connection which opened the file. The entry can therefore be removed under a different spinlock from the one protecting the list it belongs to. A concurrent traversal can then access freed struct ksmbd_lock and struct file_lock objects. Record the connection owning each lock's clist entry and hold a reference to it while the entry is linked. Use that connection and its llist_lock for unlock, rollback, close, and durable preserve. Durable reconnect assigns the new connection as the owner when publishing the locks again.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 days 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-64390, 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 · Analyzed3.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.47% · top 59% 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: High 8.8.

Affected products

  • Linux · Linux

    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < 22d38cf75b556c20b039743bdf3654d535b858be
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < 66eb3643164e5e1029907793926c132f8b5c6148
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < ea5c9bf99f626a15cc59f645dc895f2b3f01992e
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < fe20d492a69a6f79e637f438072b212e21ed3b78
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < 427faaa52b0b399940c1a88065a5c310d10dad15
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < 5fecc15a30cb9ebd310f7b52c1ab607edcea78f6
    • affected f5a544e3bab78142207e0242d22442db85ba1eff – < c1016dd1d8b2bcd1158bbaabe94a31bb7e7431fb
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .