NFS: Fix a deadlock involving nfs_release_folio()
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:
NFS: Fix a deadlock involving nfs_release_folio()
Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed.
It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.
From the CVE record · Linux
The Linux kernel can deadlock when NFSv4.1 state recovery waits on kthreadd while kthreadd attempts memory reclaim through nfs_release_folio(). The input does not describe an attacker-controlled trigger, authentication requirement, or user interaction.
Administrators running Linux kernels that use NFSv4.1 should check whether their kernel includes the fix; affected versions are not specified.