pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d67ae825a59d639e4d8b82413af84d854617a87e · < ed5d3f2f6885eb99f729e6ffd946e3aa058bd3eb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()
In nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails, the function jumps to the out_scratch label without freeing the already allocated dsaddrs list, leading to a memory leak.
Fix this by jumping to the out_err_drain_dsaddrs label, which properly frees the dsaddrs list before cleaning up other resources.
From the CVE record · Linux
In the Linux kernel’s pnfs/flexfiles code, a failed ds_versions allocation can leave an allocated dsaddrs list unfreed. This causes a memory leak; the input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with pnfs/flexfiles should check their versions; affected versions are not specified.