Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39697

NFS: Fix a race when updating an existing write

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

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39697, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < 0ff42a32784e0f2cb46a46da8e9f473538c13e1b
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < f230d40147cc37eb3aef4d50e2e2c06ea73d9a77
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < c32e3c71aaa1c1ba05da88605e2ddd493c58794f
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < 181feb41f0b268e6288bf9a7b984624d7fe2031d
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < 92278ae36935a54e65fef9f8ea8efe7e80481ace
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < 202a3432d21ac060629a760fff3b0a39859da3ea
    • affected bd37d6fce184836bd5e7cd90ce40116a4fadaf2a – < 76d2e3890fb169168c73f2e4f8375c7cc24a765e
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.242 – ≤ 5.10.*
    • unaffected 5.15.191 – ≤ 5.15.*
    • unaffected 6.1.150 – ≤ 6.1.*
    • unaffected 6.6.104 – ≤ 6.6.*
    • unaffected 6.12.44 – ≤ 6.12.*
    • unaffected 6.16.4 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39697 badge
[![CVE-2025-39697](https://cveledger.app/badge/CVE-2025-39697.svg)](https://cveledger.app/cve/CVE-2025-39697)

Record last updated .