Answer in brief
CVE-2025-39697 records a Unknown severity vulnerability in NFS: Fix a race when updating an existing write. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <0ff42a32784e0f2cb46a46da8e9f473538c13e1b || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <f230d40147cc37eb3aef4d50e2e2c06ea73d9a77 || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <c32e3c71aaa1c1ba05da88605e2ddd493c58794f || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <181feb41f0b268e6288bf9a7b984624d7fe2031d || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <92278ae36935a54e65fef9f8ea8efe7e80481ace || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <202a3432d21ac060629a760fff3b0a39859da3ea || >=bd37d6fce184836bd5e7cd90ce40116a4fadaf2a <76d2e3890fb169168c73f2e4f8375c7cc24a765e | 0ff42a32784e0f2cb46a46da8e9f473538c13e1b, f230d40147cc37eb3aef4d50e2e2c06ea73d9a77, c32e3c71aaa1c1ba05da88605e2ddd493c58794f, 181feb41f0b268e6288bf9a7b984624d7fe2031d, 92278ae36935a54e65fef9f8ea8efe7e80481ace, 202a3432d21ac060629a760fff3b0a39859da3ea, 76d2e3890fb169168c73f2e4f8375c7cc24a765e |
| Linux/Linuxgeneric | 4.14 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.