NFSv4: Don't hold the layoutget locks across multiple RPC calls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 56f487f8c8fc5d6e582b79a86fc132d050129e15 · < ea759ae0a9ae5acee677d722129710ac89cc59c1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Don't hold the layoutget locks across multiple RPC calls
When doing layoutget as part of the open() compound, we have to be careful to release the layout locks before we can call any further RPC calls, such as setattr(). The reason is that those calls could trigger a recall, which could deadlock.
From the CVE record · Linux
The Linux kernel's NFSv4 code can hold layout locks across multiple RPC calls during an open() compound operation. If a later call such as setattr() triggers a recall, the operation can deadlock. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel with NFSv4 should check their versions; the affected versions are not specified.