ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < aef151bcfa494bfe983669de2726734b534adb73| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE
FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file's sparse attribute and saves it through xattr without any permission checks.
This exposes two issues:
1) A client on a read-only share can change the sparse attribute on files it opened, even though the share is read-only. Other FSCTL write operations already check test_tree_conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE), but FSCTL_SET_SPARSE does not.
2) Even on writable shares, clients without FILE_WRITE_DATA or FILE_WRITE_ATTRIBUTES access should not modify the sparse attribute. Similar handle-level checks exist in other functions but are missing here.
Add both share-level writable check and per-handle access check. Use goto out on error to avoid leaking file references.
From the CVE record · Linux
The Linux kernel's ksmbd FSCTL_SET_SPARSE operation lacks permission checks. A client with an open file can change its sparse attribute on a read-only share, or on a writable share without FILE_WRITE_DATA or FILE_WRITE_ATTRIBUTES access. Authentication requirements are not specified.
Operators running the Linux kernel's ksmbd component should check their installations; affected versions are not specified.