smb: client: require a full NFS mode SID before reading mode bits
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f8fbfb8d09c06decde162090fac3ee220aa280 · < 38a69f08ee82c450d3e4168707fff2e317dc3ff7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: require a full NFS mode SID before reading mode bits
parse_dacl() treats an ACE SID matching sid_unix_NFS_mode as an NFS mode SID and reads sid.sub_auth[2] to recover the mode bits.
That assumes the ACE carries three subauthorities, but compare_sids() only compares min(a, b) subauthorities. A malicious server can return an ACE with num_subauth = 2 and sub_auth[] = {88, 3}, which still matches sid_unix_NFS_mode and then drives the sub_auth[2] read four bytes past the end of the ACE.
Require num_subauth >= 3 before treating the ACE as an NFS mode SID. This keeps the fix local to the special-SID mode path without changing compare_sids() semantics for the rest of cifsacl.
From the CVE record · Linux
The Linux kernel SMB client can read four bytes past an ACE when parsing an NFS mode SID with too few subauthorities. A malicious server can trigger this by returning a crafted ACE to a client parsing its ACL; the input does not specify any authentication or user-interaction requirement.
Teams running Linux kernel SMB clients should check their kernels; affected versions are not specified.