NFSD: Limit the number of concurrent async COPY operations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 · < 6a488ad7745b8f64625c6d3a24ce7e448e83f11b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Limit the number of concurrent async COPY operations
Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.
Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.
An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.
If there is need to make the mechanism more sophisticated, we can visit that in future patches.
From the CVE record · Linux
The Linux kernel's NFSD did not limit concurrent async COPY operations. A client able to issue these requests could start many long-running copies, potentially causing a denial of service. The input does not specify authentication requirements or user interaction.
Engineers running Linux systems that serve NFS should check their kernel versions; affected versions are not specified in the input.