CVE-2026-99351 in Linux
Summary
by MITRE • 11/19/2026
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: treat empty auth.unix.gid replies as negative entries
When rpc.mountd cannot resolve a uid (getpwuid() or getgrouplist() failure, e.g. while winbind or sssd is briefly unreachable), it answers the auth.unix.gid upcall with zero groups. unix_gid_parse() installs that as a valid positive entry, and svcauth_unix_set_client() then replaces the credential's group list with the empty one on every request, RPCSEC_GSS included via svcauth_gss_set_client(). One failed lookup strips that uid of all supplementary groups on every export for up to mountd's configured TTL (30 minutes by default), long after the NSS backend has recovered.
mountd cannot send an empty list for a successful lookup, since getgrouplist(3) always includes at least the user's primary group, so a zero-group reply can only mean the lookup failed. Record it as a negative entry: unix_gid_find() then returns -ENOENT and svcauth_unix_set_client() keeps the groups the RPC credential already carries. This is the fallback that commit 3fc605a2aa38 ("[PATCH] knfsd: allow the server to provide a
gid list when using AUTH_UNIX authentication") promised when no answer is available, and the same state try_to_negate_entry() already creates when no listener holds the channel open.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/19/2026
The vulnerability described involves a critical flaw in the Linux kernel's Sun Remote Procedure Call (RPC) implementation, specifically within the user space daemon rpc.mountd which handles NFS mount requests. The core issue stems from how the system processes responses to authentication upcalls when resolving group identifiers for remote users. When an administrator configures NFS exports with security options that require mapping local Unix groups to remote UIDs or GIDs, the server relies on Name Service Switch (NSS) backends such as winbind or System Security Services Daemon (sssd) to resolve these identities. In scenarios where these backend services are temporarily unreachable due to network issues, service restarts, or configuration errors, the lookup functions getpwuid() and getgrouplist() fail to return valid data. Instead of treating this failure appropriately, the existing logic interprets an empty group list returned by auth.unix.gid as a successful resolution resulting in zero supplementary groups for that user.
This misinterpretation leads to severe operational impacts on NFS clients accessing shared resources. The function unix_gid_parse() incorrectly installs the empty group list as a valid positive entry within the credential cache. Consequently, every subsequent RPC request from this client triggers svcauth_unix_set_client(), which replaces the existing, potentially correct set of supplementary groups with an empty one. This stripping effect persists for the duration of the mountd's configured Time To Live (TTL), typically thirty minutes by default. During this window, even after the NSS backend has recovered and become reachable again, the server continues to enforce access control decisions based on a credential that lacks all supplementary group memberships. For users who rely heavily on group-based permissions for read or write access to NFS shares, this results in an effective denial of service where legitimate access is revoked without any change in network connectivity or user credentials.
From a technical perspective, the flaw violates fundamental assumptions about POSIX identity resolution standards. The function getgrouplist(3) is designed such that it always includes at least the primary group ID associated with the user; therefore, an empty list of groups returned by this call can only logically indicate a lookup failure rather than a valid state where a user belongs to no groups. By failing to distinguish between a successful resolution yielding zero supplementary groups and a failed resolution returning null or empty data, the kernel exposes systems to unintended privilege degradation. This behavior aligns with CWE-20 Improper Input Validation, as the system fails to validate that an empty response from a critical identity lookup constitutes an error condition rather than valid state information. Furthermore, it impacts availability by causing unexpected access denials for authenticated users, which can be categorized under ATT&CK technique T1534 if exploited in conjunction with other misconfigurations to disrupt service continuity, although primarily this is a reliability and integrity issue within the authentication subsystem.
The resolution involves modifying unix_gid_parse() to recognize that an empty group list signifies a negative lookup result rather than a valid positive entry. By recording these instances as negative entries, the subsequent call to unix_gid_find() returns -ENOENT, signaling that no cached mapping exists for this specific query attempt. This triggers svcauth_unix_set_client() to retain the groups already carried by the RPC credential instead of overwriting them with an empty set. This approach restores the fallback behavior originally intended in commit 3fc605a2aa38, which aimed to allow servers to provide gid lists while maintaining robustness against missing answers. It also aligns with the state managed by try_to_negate_entry(), ensuring consistency across different code paths that handle channel closures or listener unavailability.
To mitigate this vulnerability and prevent similar issues in related systems, administrators should ensure high availability of NSS backends like winbind or sssd through proper clustering and load balancing configurations to minimize lookup failures. Additionally, monitoring tools should be configured to alert on frequent authentication upcall timeouts or errors, allowing for rapid intervention before the TTL period causes widespread access disruptions. System integrators reviewing NFS server implementations must ensure that identity resolution logic strictly validates response codes from getpwuid() and getgrouplist(), treating empty results as failures rather than valid zero-group states. This ensures that credentials are not inadvertently stripped of their group memberships, preserving the integrity of access control lists and maintaining consistent service availability for all authenticated users accessing NFS resources.