CVE-2025-39697

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-09-05. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

September 5, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76d2e3890fb169168c73f2e4f8375c7cc24a765e
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/202a3432d21ac060629a760fff3b0a39859da3ea
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92278ae36935a54e65fef9f8ea8efe7e80481ace
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/181feb41f0b268e6288bf9a7b984624d7fe2031d
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c32e3c71aaa1c1ba05da88605e2ddd493c58794f
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f230d40147cc37eb3aef4d50e2e2c06ea73d9a77
generic

NFS: Fix a race when updating an existing write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ff42a32784e0f2cb46a46da8e9f473538c13e1b

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-106.106~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1049.52~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-05-21ubuntu
redhatkernel-0:5.14.0-570.79.1.el9_62026-01-19redhat
redhatkernel-0:4.18.0-193.178.1.el8_22025-12-17redhat
redhatkernel-0:4.18.0-477.122.1.el8_82025-12-10redhat
redhatkernel-0:4.18.0-305.179.1.el8_42025-12-04redhat
redhatkernel-0:4.18.0-372.170.1.el8_62025-11-25redhat
redhatkernel-rt-0:4.18.0-553.85.1.rt7.426.el8_102025-11-24redhat
redhatkernel-0:4.18.0-553.85.1.el8_102025-11-24redhat
redhatkernel-0:5.14.0-427.100.1.el9_42025-11-19redhat
redhatkernel-0:5.14.0-611.8.1.el9_72025-11-17redhat
redhatkernel-0:5.14.0-70.153.1.el9_02025-11-12redhat
redhatkernel-0:6.12.0-124.9.1.el10_12025-11-12redhat
redhatkernel-rt-0:5.14.0-284.146.1.rt14.431.el9_22025-11-12redhat
redhatkernel-rt-0:5.14.0-70.153.1.rt21.225.el9_02025-11-12redhat
redhatkernel-0:5.14.0-284.146.1.el9_22025-11-12redhat
redhatkernel-0:6.12.0-55.41.1.el10_02025-10-27redhat
linuxKernel @ 5.10.242osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)5.10.244-1
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)6.1.153-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (43 versions)6.1.153-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+16.12.48-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (60 versions)6.16.5-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 5× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 163 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-07 11:48 UTCOSV refresh
  3. 2026-09-06 13:46 UTCEPSS rescore
  4. 2026-09-04 05:05 UTCEPSS rescore
  5. 2026-09-02 14:11 UTCEPSS rescore
  6. 2026-09-01 13:53 UTCEPSS rescore
  7. 2026-09-01 04:38 UTCEPSS rescore
  8. 2026-08-30 19:16 UTCEPSS rescore
  9. 2026-08-30 01:21 UTCEPSS rescore
  10. 2026-08-28 21:40 UTCEPSS rescore
  11. 2026-08-27 14:24 UTCEPSS rescore
  12. 2026-08-26 14:45 UTCEPSS rescore
  13. 2026-08-25 13:48 UTCEPSS rescore
  14. 2026-08-23 00:18 UTCEPSS rescore
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-20 22:54 UTCEPSS rescore
  17. 2026-08-20 20:31 UTCOSV refresh
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-19 17:03 UTCEPSS rescore
  20. 2026-08-18 13:47 UTCEPSS rescore
  21. 2026-08-17 13:46 UTCEPSS rescore
  22. 2026-08-16 14:55 UTCEPSS rescore
  23. 2026-08-16 02:13 UTCEPSS rescore
  24. 2026-08-15 01:29 UTCEPSS rescore
  25. 2026-08-13 21:59 UTCEPSS rescore
Show 75 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-08 16:36 UTCEPSS rescore
  4. 2026-08-07 16:26 UTCEPSS rescore
  5. 2026-08-06 13:46 UTCEPSS rescore
  6. 2026-08-05 12:58 UTCEG score recompute
  7. 2026-08-05 12:58 UTCVendor advisory
  8. 2026-08-05 12:58 UTCGHSA enrichment
  9. 2026-08-04 15:09 UTCEPSS rescore
  10. 2026-08-04 10:37 UTCEPSS rescore
  11. 2026-08-03 10:35 UTCEPSS rescore
  12. 2026-08-02 02:26 UTCEPSS rescore
  13. 2026-08-01 04:15 UTCEPSS rescore
  14. 2026-07-30 16:27 UTCEPSS rescore
  15. 2026-07-30 06:55 UTCEG score recompute
  16. 2026-07-30 06:55 UTCVendor advisory
  17. 2026-07-30 06:54 UTCGHSA enrichment
  18. 2026-07-30 06:24 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  19. 2026-07-30 01:29 UTCEPSS rescore
  20. 2026-07-28 15:35 UTCEPSS rescore
  21. 2026-07-27 12:39 UTCOSV refresh
  22. 2026-07-25 14:17 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-24 14:17 UTCEPSS rescore
  25. 2026-07-23 02:55 UTCEG score recompute
  26. 2026-07-22 14:07 UTCEPSS rescore
  27. 2026-07-22 14:07 UTCEPSS rescore
  28. 2026-07-21 15:24 UTCEPSS rescore
  29. 2026-07-20 17:07 UTCEPSS rescore
  30. 2026-07-19 14:30 UTCEPSS rescore
  31. 2026-07-19 14:30 UTCEPSS rescore
  32. 2026-07-18 10:04 UTCEPSS rescore
  33. 2026-07-18 10:04 UTCEPSS rescore
  34. 2026-07-16 17:02 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-13 22:29 UTCEPSS rescore
  38. 2026-07-13 22:29 UTCEPSS rescore
  39. 2026-07-12 05:46 UTCEPSS rescore
  40. 2026-07-11 08:27 UTCEPSS rescore
  41. 2026-07-11 08:27 UTCEPSS rescore
  42. 2026-07-10 07:23 UTCOSV refresh
  43. 2026-07-09 19:09 UTCEPSS rescore
  44. 2026-07-09 19:09 UTCEPSS rescore
  45. 2026-07-07 13:45 UTCEPSS rescore
  46. 2026-07-06 02:23 UTCEPSS rescore
  47. 2026-07-05 02:30 UTCEPSS rescore
  48. 2026-07-04 06:30 UTCEPSS rescore
  49. 2026-06-30 23:22 UTCEPSS rescore
  50. 2026-06-30 23:22 UTCEPSS rescore
  51. 2026-06-29 14:06 UTCEPSS rescore
  52. 2026-06-29 14:06 UTCEPSS rescore
  53. 2026-06-28 14:07 UTCEPSS rescore
  54. 2026-06-28 14:07 UTCEPSS rescore
  55. 2026-06-28 04:55 UTCEPSS rescore
  56. 2026-06-28 04:55 UTCEPSS rescore
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-27 03:08 UTCEPSS rescore
  59. 2026-06-25 13:49 UTCEPSS rescore
  60. 2026-06-25 13:49 UTCEPSS rescore
  61. 2026-06-24 14:04 UTCEPSS rescore
  62. 2026-06-24 14:04 UTCEPSS rescore
  63. 2026-06-23 21:32 UTCEPSS rescore
  64. 2026-06-23 21:32 UTCEPSS rescore
  65. 2026-06-22 14:25 UTCEPSS rescore
  66. 2026-06-22 14:25 UTCEPSS rescore
  67. 2026-06-21 17:12 UTCOSV refresh
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 14:56 UTCEPSS rescore
  70. 2026-06-21 01:59 UTCEPSS rescore
  71. 2026-06-21 01:59 UTCEPSS rescore
  72. 2026-06-19 19:25 UTCEPSS rescore
  73. 2026-06-19 19:25 UTCEPSS rescore
  74. 2026-06-18 17:52 UTCEPSS rescore
  75. 2026-06-18 17:52 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-39697?
CVE-2025-39697 is a medium vulnerability published on September 5, 2025. 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 nfsinoderemove_request() from succeeding until we actually…
When was CVE-2025-39697 disclosed?
CVE-2025-39697 was first published in the National Vulnerability Database on September 5, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39697 actively exploited?
CVE-2025-39697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.6% of all scored CVEs.
What is the CVSS score of CVE-2025-39697?
CVE-2025-39697 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2025-39697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39697, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-39697

Explore →

Is Your Infrastructure Affected by CVE-2025-39697?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.