ksmbd: use opener credentials for delete-on-close
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f44158485826c076335d6860d35872271a83791d · < 52e2f21911158ec961cd5aae19c56460db382af0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: use opener credentials for delete-on-close
Delete-on-close can be completed by deferred or durable handle teardown, where no request work is available. Both the base-file unlink and the ADS xattr removal consequently run with the ksmbd worker credentials and can bypass filesystem permission checks.
Run both operations with the credentials captured in struct file when the handle was opened. This preserves the authenticated user's fsuid, fsgid, supplementary groups and capability restrictions at final close.
From the CVE record · Linux
In the Linux kernel’s ksmbd component, delete-on-close during deferred or durable handle teardown can run with worker credentials instead of the authenticated user’s credentials. This can let base-file deletion or ADS xattr removal bypass filesystem permission checks when no request work is available.
Engineers running Linux kernels with ksmbd should check whether their kernel is affected; affected versions were not provided.