ksmbd: require 3 sub-authorities before reading sub_auth[2]
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < 9401f86a224f37b50e6a3ccf1d46a70d5ef8af0a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: require 3 sub-authorities before reading sub_auth[2]
parse_dacl() compares each ACE SID against sid_unix_NFS_mode and on match reads sid.sub_auth[2] as the file mode. If sid_unix_NFS_mode is the prefix S-1-5-88-3 with num_subauth = 2 then compare_sids() compares only min(num_subauth, 2) sub-authorities so a client SID with num_subauth = 2 and sub_auth = {88, 3} will match.
If num_subauth = 2 and the ACE is placed at the very end of the security descriptor, sub_auth[2] will be 4 bytes past end_of_acl. The out-of-band bytes will then be masked to the low 9 bits and applied as the file's POSIX mode, probably not something that is good to have happen.
Fix this up by forcing the SID to actually carry a third sub-authority before reading it at all.
From the CVE record · Linux
The Linux kernel’s ksmbd can read past the end of an access control list when an ACE at the end of a security descriptor contains a specially formed SID with only two sub-authorities. The out-of-bounds bytes can then be applied as the file’s POSIX mode. The input does not specify whether authentication is required.
Operators running Linux kernels with ksmbd should check whether their kernel includes the fix; affected versions are not specified.