All reports
Medium

kernel: NFSv4: Fix a deadlock when recovering state on a sillyrenamed file

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-21900

Probability of exploitation in the next 30 days: 0.36%

FIRST EPSS · 2026-11-20

Description

In 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.

A flaw was found in the Linux kernel's NFSv4 (Network File System version 4) client. This flaw allows a Denial of Service (DoS) when a local application closes a deleted file while the client recovers its state during an NFS server reboot. A race condition during state recovery causes an internal locking conflict (deadlock), hanging affected client filesystem operations.