First published: Tue Apr 01 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=6.11<6.12.18 | |
Linux Kernel | >=6.13<6.13.6 | |
Linux Kernel | =6.14-rc1 | |
Linux Kernel | =6.14-rc2 | |
Linux Kernel | =6.14-rc3 | |
Linux Kernel | =6.14-rc4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-21900 has a high severity rating due to the potential for system deadlocks affecting server recovery operations.
To fix CVE-2025-21900, update your Linux kernel to versions 6.12.18, 6.13.6, or later as these releases contain the necessary patches.
CVE-2025-21900 affects Linux kernel versions from 6.11 up to 6.14-rc4, specifically the versions outlined between those ranges.
CVE-2025-21900 impacts systems running the Linux kernel, particularly those utilizing NFSv4 with sillyrenamed files.
As of now, there are no publicly known exploits specifically targeting CVE-2025-21900, but its vulnerability could be leveraged in certain scenarios.