NFSv4: Fix a deadlock when recovering state on a sillyrenamed file
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 |
|
|
6.12.186.13.66.14In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Fix a deadlock when recovering state on a sillyrenamed file
If the file is sillyrenamed, and slated for delete on close, it is possible for a server reboot to triggeer an open reclaim, with can again race with the application call to close(). When that happens, the call to put_nfs_open_context() can trigger a synchronous delegreturn call which deadlocks because it is not marked as privileged.
Instead, ensure that the call to nfs4_inode_return_delegation_on_close() catches the delegreturn, and schedules it asynchronously.
From the CVE record · Linux
The Linux kernel’s NFSv4 state recovery can deadlock when a server reboot triggers an open reclaim for a sillyrenamed file while an application closes it. The input does not describe an attacker, authentication requirements, or a user-interaction requirement.
Engineers running Linux systems that use NFSv4 should check whether their kernel is affected; affected versions are not specified.