Linux kernel memory leak in pNFS data-server address cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s NFSv4/pnfs layout drivers can leak a data-server address entry’s netid when draining a decoded address list. This occurs when a data server is already cached or on an error exit; the input does not describe an attacker path or authentication requirements.
Operators running Linux kernels with NFSv4/pnfs should check their kernel’s status; affected versions are not specified.