ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d · < 1c8951963d8ed357f70f59e0ad4ddce2199d2016| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
The SMB2 open lookup is rooted at the share with LOOKUP_BENEATH, but the create/mkdir/hardlink sink is not: ksmbd_vfs_kern_path_create() builds an absolute path with convert_to_unix_name() and resolves it from AT_FDCWD via start_creating_path(), so a ".." component is walked from the real filesystem root and escapes the export.
An authenticated client races a missing path component so the rooted open lookup returns -ENOENT (taking the create branch) while the same component is present (a directory) when the create walk runs; the create then resolves ".." out of the share.
Root the create walk at the share like the lookup and rename paths already are: resolve the parent with vfs_path_parent_lookup(..., LOOKUP_BENEATH, &share_conf->vfs_path) and create the final component with start_creating_noperm(). convert_to_unix_name() then has no callers and is removed.
From the CVE record · Linux
The Linux kernel's ksmbd create path can resolve a path outside an SMB share. An authenticated SMB client can race a missing path component to make a create operation escape the share; the attack requires network access and no user interaction is described.
Operators running Linux systems with ksmbd should check their kernel; affected versions are not specified.