CVE-2025-39697: NFS: Fix a race when updating an existing write
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix a race when updating an existing write
After nfslockandjoinrequests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfsinoderemoverequest() from succeeding until we actually lock the page group. The reason is that whoever called nfsinoderemoverequest() doesn't necessarily have a lock on the page group head.
So in order to avoid races, let's take the page group lock earlier in nfslockandjoinrequests(), and hold it across the removal of the request in nfsinoderemoverequest().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39697?
The severity of CVE-2025-39697 is classified as moderate due to its impact on the stability of NFS operations.
How do I fix CVE-2025-39697?
To fix CVE-2025-39697, you should update the Linux kernel to a version that includes the patch for this vulnerability.
What systems are affected by CVE-2025-39697?
CVE-2025-39697 affects various versions of the Linux kernel that implement NFS functionality.
What is the nature of the issue in CVE-2025-39697?
CVE-2025-39697 involves a race condition when updating an existing write in the NFS implementation of the Linux kernel.
Can CVE-2025-39697 be exploited remotely?
Yes, CVE-2025-39697 can be exploited remotely by an attacker with access to a vulnerable NFS service.