ksmbd: deny access for an empty DACL instead of granting the request
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel de0cffef897c1c232ed973f89928cd6c93d0b1e3, Kernel 0c96f614876e251ae9d6764e8d52d6544fef0424, Kernel 28db998d396a9b2e6e9ecf69c2a201b8f06df2b2 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: deny access for an empty DACL instead of granting the request smb_check_perm_dacl() returns the access mask it computes to the SMB2 CREATE handler, which uses it as the granted access for the open. For a security descriptor whose DACL is present but contains no ACEs, the function is supposed to deny access: an empty (non-NULL) DACL grants no access to anyone except the object owner's implicit READ_CONTROL and WRITE_DAC (MS-DTYP 2.4.5). The empty-DACL branch only denies when both - the DACL has no trailing bytes (pdacl_size == sizeof(struct smb_acl)), and - the request contains bits beyond READ_CONTROL / WRITE_DAC. In every other case it takes the shared "goto err_out" with rc still 0, which returns success without modifying *pdaccess, so the caller grants the full requested access. Three problems follow: - The READ_CONTROL / WRITE_DAC carve-out models the owner's implicit rights, but the check runs before is_owner is computed, so those rights are handed to *every* caller, not just the owner. For READ_CONTROL the SMB2 CREATE path does not fall back to inode_permission(), so any user can read the security descriptor of an object whose empty DACL is meant to deny them. - A request of exactly READ_CONTROL and/or WRITE_DAC is granted to any caller. WRITE_DAC lets the handle rewrite the DACL. - A DACL that declares zero ACEs but carries trailing bytes (pdacl_size > sizeof(struct smb_acl)) skips the deny entirely and is granted whatever was requested. On shares where the NT ACL is the authoritative access control -- e.g. "force user" shares, where every client maps to one POSIX identity so POSIX cannot distinguish users -- this is an access-control bypass. Compute is_owner before the empty-DACL branch and deny access from an empty DACL unless the caller is the owner requesting no more than READ_CONTROL / WRITE_DAC.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <de0cffef897c1c232ed973f89928cd6c93d0b1e3, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <0c96f614876e251ae9d6764e8d52d6544fef0424, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <28db998d396a9b2e6e9ecf69c2a201b8f06df2b2, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <be67941493114d1145d16088938bf589e34f111b, =5.15 | de0cffef897c1c232ed973f89928cd6c93d0b1e3, 0c96f614876e251ae9d6764e8d52d6544fef0424, 28db998d396a9b2e6e9ecf69c2a201b8f06df2b2, be67941493114d1145d16088938bf589e34f111b |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.15.0 <6.12.117 | 6.18.61, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket