Linux ksmbd share root removal via empty link paths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: prevent share root removal through empty paths
A FileLinkInformation request can supply "/" as the new link name. smb2_get_name() strips the trailing slash and passes an empty string to ksmbd_vfs_kern_path_start_removing().
ksmbd_vfs_path_lookup() resolves an empty pathname as the configured share path, without LOOKUP_BENEATH. With ReplaceIfExists set, smb2_create_link() can therefore remove the share root from its parent before link creation fails. An authenticated client with a writable share and DELETE access to a file can trigger this if the share root is empty and the mapped user has write and search permission on its parent directory.
Return -EINVAL for empty pathnames when for_remove is set, before resolving the share path or acquiring removal resources. Ordinary lookups continue to accept empty pathnames for opening the share root.
From the CVE record · Linux
Linux kernel ksmbd can resolve an empty removal path to the configured share root. An authenticated client can cause the share root to be removed by sending a FileLinkInformation request with a new link name of "/" and ReplaceIfExists set, if the share is writable, the client has DELETE access to a file, the share root is empty, and the mapped user can write to and search its parent directory.
Teams running Linux kernels with ksmbd writable shares should check whether their kernels include the fix; affected versions are not specified.