CVE-2026-64390 Affecting linux-6.12 package, versions <6.12.100-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LINUX612-18579236
- published7 Aug 2026
- disclosed25 Jul 2026
Introduced: 25 Jul 2026
CVE-2026-64390 (opens in a new tab)How to fix?
Upgrade Echo:latest linux-6.12 to version 6.12.100-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.
References
- https://advisory.echohq.com/cve/CVE-2026-64390
- https://git.kernel.org/stable/c/22d38cf75b556c20b039743bdf3654d535b858be
- https://git.kernel.org/stable/c/427faaa52b0b399940c1a88065a5c310d10dad15
- https://git.kernel.org/stable/c/5fecc15a30cb9ebd310f7b52c1ab607edcea78f6
- https://git.kernel.org/stable/c/66eb3643164e5e1029907793926c132f8b5c6148
- https://git.kernel.org/stable/c/c1016dd1d8b2bcd1158bbaabe94a31bb7e7431fb
- https://git.kernel.org/stable/c/ea5c9bf99f626a15cc59f645dc895f2b3f01992e
- https://git.kernel.org/stable/c/fe20d492a69a6f79e637f438072b212e21ed3b78