CVE-2026-90162

published 17 Sep 2026 · updated 1 Nov 2026

ksmbd: defer publishing granted locks to prevent UAF/double-free race

8.8HighCVSS 8.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 29f74f0f2e6df3b393b7b66e810136d0c64e3c59, Kernel 65f54ed0289e9a57e6c60b14347ccea4c318f1fc, Kernel a1d26dfb32919088e3638dca01068df3c4507433 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: defer publishing granted locks to prevent UAF/double-free race In smb2_lock(), mid-batch granted locks are published to connection-wide (conn->lock_list) and file-wide (fp->lock_list) lists immediately upon vfs_lock_file() success, while also remaining tracked on the stack-local rollback_list. If a subsequent element in the same SMB2_LOCK request array fails validation or execution, the thread jumps to out: and walks rollback_list to undo previously granted locks. However, because the granted lock was already published to conn->lock_list, a concurrent UNLOCK request on the same connection can find the lock object and kfree() it before the rollback loop executes. When the granting thread subsequently walks rollback_list, it dereferences and frees the already-freed ksmbd_lock structure, resulting in a Use-After-Free and Double-Free (on both ksmbd_lock and struct file_lock). Fix this by deferring the publication of granted locks to conn->lock_list and fp->lock_list until after the entire array of lock elements has been processed without error. Mid-batch grants remain tracked exclusively on the request-local rollback_list until the whole batch succeeds, eliminating the race window.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.15, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <29f74f0f2e6df3b393b7b66e810136d0c64e3c59, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <65f54ed0289e9a57e6c60b14347ccea4c318f1fc, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <a1d26dfb32919088e3638dca01068df3c4507433, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <b68d4bb6b03a667c305626bd2c242fd162bac17e, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <f1371a140722c1d6868f9acf69d601de7d4142bf, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <ff6870cf3b7eccc69d03cbb6f23e3995d96e9a8d29f74f0f2e6df3b393b7b66e810136d0c64e3c59, 65f54ed0289e9a57e6c60b14347ccea4c318f1fc, a1d26dfb32919088e3638dca01068df3c4507433, b68d4bb6b03a667c305626bd2c242fd162bac17e, f1371a140722c1d6868f9acf69d601de7d4142bf, ff6870cf3b7eccc69d03cbb6f23e3995d96e9a8d

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90162 severity on Zeptric[![CVE-2026-90162](https://zeptric.io/badge/cve/CVE-2026-90162.svg)](https://zeptric.io/cve/CVE-2026-90162)