CVE-2026-99743 in Linux
Summary
by MITRE • 11/20/2026
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: grant a POSIX ACL group entry only to the group's members
When no ACE of the DACL matches the caller, Everyone or Authenticated Users, smb_check_perm_dacl() falls back to the file's POSIX ACL. It takes the first ACL_USER or ACL_GROUP entry whose id equals the caller's uid. For ACL_GROUP, this compares a gid with the caller's uid. A numerical match grants the group's permissions even when the caller is not a member.
Match a group entry only when the caller is also in the group.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/20/2026
The ksmbd kernel module, which provides Server Message Block protocol support for Linux systems, contained a critical access control logic flaw within its Discretionary Access Control List evaluation routine. Specifically, the smb_check_perm_dacl function handles permission checks by first attempting to match an Access Control Entry against the caller's identity. When no standard DACL entry matches the user or group identifiers of the requesting process, the system falls back to evaluating POSIX ACLs associated with the file object. This fallback mechanism is designed to ensure that files configured with extended POSIX permissions are correctly enforced even when traditional Windows-style access control entries do not apply.
The technical vulnerability arises from an incorrect comparison logic within this POSIX ACL evaluation path. When processing a group-based Access Control Entry, specifically one identified by the ACL_GROUP tag, the code erroneously compares the Group Identifier stored in the ACL entry directly against the User Identifier of the caller. This is a fundamental category error where two distinct identity attributes are treated as equivalent for authorization purposes. Consequently, if the numerical value of the file's group ID happens to match the numerical user ID of any process attempting to access that file, the system grants the permissions defined in that specific ACL_GROUP entry regardless of whether the calling process actually belongs to that group membership list.
This flaw results in a significant unauthorized information disclosure and privilege escalation vector classified under CWE-269 Improper Privilege Management. An attacker with knowledge of the numeric identifiers on the target system can craft requests where their user ID matches a sensitive file's group ID. By doing so, they bypass intended access restrictions and gain read or write permissions to files that should be restricted to members of that specific group only. This undermines the integrity of the POSIX ACL security model implemented within ksmbd, allowing lateral movement or data exfiltration in environments where strict role-based access controls are relied upon for compliance with standards such as NIST SP 800-53 AC-6 Least Privilege.
The operational impact extends beyond simple file permission bypasses to potential compromise of system integrity and confidentiality within shared network directories. Since ksmbd is often used in enterprise environments to provide SMB/CIFS shares, this vulnerability allows any authenticated user with a coincidentally matching UID-GID pair to access restricted resources. This can lead to the exposure of sensitive configuration files, private documents, or other critical data assets that are protected by group-based restrictions rather than owner-only permissions. The flaw effectively neutralizes the security boundary provided by POSIX ACLs for group entries in this specific fallback scenario.
To mitigate this vulnerability, system administrators and developers must ensure that the ksmbd module is updated to versions where the smb_check_perm_dacl function has been corrected to properly validate group membership rather than relying on numerical ID equality. The fix involves modifying the logic so that when an ACL_GROUP entry is encountered, the system checks whether the caller's user identifier is listed as a member of the corresponding group via standard OS-level group resolution mechanisms such as getgrgid or equivalent kernel APIs. Until patches are applied, organizations should consider restricting access to ksmbd shares through network segmentation and firewall rules, limiting exposure to trusted networks only, while also auditing file permissions on shared directories for any potential exploitation based on UID-GID collisions within the local system environment.