NFSD: fix hang in nfsd4_shutdown_callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 66af25799940b26efd41ea6e648f75c41a48a2c2 · < e88d2451cd42e025465d6b51fd716a47b0b3800d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSD: fix hang in nfsd4_shutdown_callback
If nfs4_client is in courtesy state then there is no point to send the callback. This causes nfsd4_shutdown_callback to hang since cl_cb_inflight is not 0. This hang lasts about 15 minutes until TCP notifies NFSD that the connection was dropped.
This patch modifies nfsd4_run_cb_work to skip the RPC call if nfs4_client is in courtesy state.
From the CVE record · Linux
The Linux kernel's NFSD callback shutdown can hang when an NFSv4 client is in courtesy state and a callback remains in flight. The hang lasts about 15 minutes, until TCP reports that the connection was dropped. The input does not establish whether an attacker can trigger this or what access would be required.
Operators running the Linux kernel with NFSD should check whether their version is affected; affected versions are not specified.