In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix a race when updating an existing write
After nfs_lock_and_join_requests() tests for whether the request is
still attached to the mapping, nothing prevents a call to
nfs_inode_remove_request() from succeeding until we actually lock the
page group.
The reason is that whoever called nfs_inode_remove_request() 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
nfs_lock_and_join_requests(), and hold it across the removal of the
request in nfs_inode_remove_request().
Metrics
Affected Vendors & Products
References
History
Mon, 08 Sep 2025 06:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Sat, 06 Sep 2025 09:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Linux
Linux linux Kernel |
|
Vendors & Products |
Linux
Linux linux Kernel |
Sat, 06 Sep 2025 00:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Fri, 05 Sep 2025 17:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a race when updating an existing write After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_remove_request() 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 nfs_lock_and_join_requests(), and hold it across the removal of the request in nfs_inode_remove_request(). | |
Title | NFS: Fix a race when updating an existing write | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-09-05T17:21:03.178Z
Updated: 2025-09-08T06:22:02.034Z
Reserved: 2025-04-16T07:20:57.115Z
Link: CVE-2025-39697

No data.

Status : Awaiting Analysis
Published: 2025-09-05T18:15:46.623
Modified: 2025-09-08T16:25:38.810
Link: CVE-2025-39697
