CVE-2026-64390ksmbd: track the connection owning a byte-range lock
- 8.8HighCVSS base score
- 0.47%Exploitation in 30 daysEPSS · top 59% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 23 days later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High8.8 | CVSS: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)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < 22d38cf75b556c20b039743bdf3654d535b858be
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < 66eb3643164e5e1029907793926c132f8b5c6148
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < ea5c9bf99f626a15cc59f645dc895f2b3f01992e
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < fe20d492a69a6f79e637f438072b212e21ed3b78
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < 427faaa52b0b399940c1a88065a5c310d10dad15
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < 5fecc15a30cb9ebd310f7b52c1ab607edcea78f6
- affected f5a544e3bab78142207e0242d22442db85ba1eff – < c1016dd1d8b2bcd1158bbaabe94a31bb7e7431fb
- 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
- https://git.kernel.org/stable/c/22d38cf75b556c20b039743bdf3654d535b858be (opens in a new tab)
- https://git.kernel.org/stable/c/66eb3643164e5e1029907793926c132f8b5c6148 (opens in a new tab)
- https://git.kernel.org/stable/c/ea5c9bf99f626a15cc59f645dc895f2b3f01992e (opens in a new tab)
- https://git.kernel.org/stable/c/fe20d492a69a6f79e637f438072b212e21ed3b78 (opens in a new tab)
- https://git.kernel.org/stable/c/427faaa52b0b399940c1a88065a5c310d10dad15 (opens in a new tab)
- https://git.kernel.org/stable/c/5fecc15a30cb9ebd310f7b52c1ab607edcea78f6 (opens in a new tab)
- https://git.kernel.org/stable/c/c1016dd1d8b2bcd1158bbaabe94a31bb7e7431fb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48934 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64390)Record last updated .