CVE-2026-99376 in Linux
Summary
by MITRE • 11/19/2026
In the Linux kernel, the following vulnerability has been resolved:
NFSv4/pnfs: Free the netid when draining a data-server address list
nfs4_pnfs_ds_addr_free() releases all three of an address entry's allocations, but the four sites that drain a decoded list before it reaches a data server open-code the loop and free only da_remotestr and the entry, leaking da_netid. Both layout drivers drain that list when nfs4_pnfs_ds_add() returned a data server already in the cache, and again on their error exits.
Lift the drain into nfs4_pnfs_ds_addr_list_free() so an address list has one owner. A striping mount reaches the cached case on nearly every GETDEVICEINFO, since many deviceIDs name the same data servers.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/19/2026
The Linux kernel contains a memory management flaw within the Network File System version four (NFSv4) and parallel NFS (pnfs) subsystems that results in resource leaks during address list processing. Specifically, the vulnerability resides in how certain code paths handle the cleanup of data-server address entries when they are drained from a decoded list before being assigned to an active data server. The function nfs4_pnfs_ds_addr_free() is designed to properly release all three memory allocations associated with an address entry: da_remotestr, da_netid, and the entry structure itself. However, four distinct sites in the codebase manually drain this list by implementing a custom loop that only frees da_remotestr and the entry pointer, neglecting to free the da_netid string. This oversight leads to a persistent memory leak every time such a drainage operation occurs.
The operational impact of this vulnerability is primarily related to resource exhaustion over extended periods or under high load conditions. The leakage occurs in two specific scenarios within the pnfs layout drivers: first when nfs4_pnfs_ds_add() detects that a data server is already present in the cache, and second during error exit paths where cleanup routines are invoked but fail to release all allocated memory segments. In environments utilizing striping mounts, which distribute file operations across multiple servers for performance optimization, this issue becomes particularly acute. Because many device identifiers often refer to the same physical or virtual data servers, the cached case is triggered on nearly every GETDEVICEINFO RPC call. Consequently, frequent network interactions with NFSv4/pnfs storage can lead to gradual kernel memory consumption increases, potentially degrading system stability and performance if left unaddressed in long-running deployments.
From a technical classification perspective, this flaw aligns with CWE-401, which describes the failure to release memory after it has been finished being used, leading to resource leaks. The vulnerability exploits improper cleanup logic within kernel-space networking components rather than exploiting input validation or authentication bypasses. In terms of adversarial tactics, while not directly exploitable for remote code execution in its current form, such memory leaks can be leveraged as part of a denial-of-service campaign by an attacker who induces frequent GETDEVICEINFO requests to accelerate the exhaustion of kernel memory resources. This falls under MITRE ATT&CK technique T1499, Endpoint Denial of Service, specifically resource hijacking through inefficient resource management.
The resolution involves refactoring the cleanup logic to ensure a single owner for each address list instance. By lifting the drain operation into nfs4_pnfs_ds_addr_list_free(), developers have centralized the deallocation process, ensuring that all three components of an address entry are consistently freed regardless of whether the server was found in cache or if an error occurred during processing. This change eliminates the redundant and incomplete manual loops previously scattered across multiple layout drivers. System administrators should apply kernel updates containing this fix to prevent potential memory leaks in NFSv4/pnfs environments, particularly those relying on striping configurations where frequent device information retrieval is standard operational behavior.