Skip to content
Noroxi
CVE-2025-39697· NVD / CVE Program· CNA Linux

NFS: Fix a race when updating an existing write

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0ff42a32784e0f2cb46a46da8e9f473538c13e1b, 181feb41f0b268e6288bf9a7b984624d7fe2031d, 202a3432d21ac060629a760fff3b0a39859da3ea; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 0ff42a32784e0f2cb46a46da8e9f473538c13e1b, 181feb41f0b268e6288bf9a7b984624d7fe2031d, 202a3432d21ac060629a760fff3b0a39859da3ea; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Sep 5, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.7
CNA · Linux
7.8
3.1 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39697

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.11 and later · before 5.15.191
  • linux linux kernel5.16 and later · before 6.1.150
  • linux linux kernel6.2 and later · before 6.6.104
  • linux linux kernel4.14 and later · before 5.10.242
  • linux linux kernel6.13 and later · before 6.16.4
  • linux linux kernel6.7 and later · before 6.12.44
  • linux linux kernel6.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.14affected
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before 0ff42a32784e0f2cb46a46da8e9f473538c13e1baffected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before f230d40147cc37eb3aef4d50e2e2c06ea73d9a77affected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before c32e3c71aaa1c1ba05da88605e2ddd493c58794faffected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before 181feb41f0b268e6288bf9a7b984624d7fe2031daffected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before 92278ae36935a54e65fef9f8ea8efe7e80481aceaffected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before 202a3432d21ac060629a760fff3b0a39859da3eaaffected · git
    • bd37d6fce184836bd5e7cd90ce40116a4fadaf2a and later · before 76d2e3890fb169168c73f2e4f8375c7cc24a765eaffected · git
    • before 4.14not affected · semver
    • 5.10.242 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.85.1.el8_104.18.0-553.85.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.85.1.rt7.426.el8_104.18.0-553.85.1.rt7.426.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39695Sep 5, 2025 · RDMA/rxe: Flush delayed SKBs while releasing RXE resources
    22Monitor
  • ← EarlierCVE-2025-39696Sep 5, 2025 · ALSA: hda: tas2781: Fix wrong reference of tasdevice_priv
    22Monitor
  • Later →CVE-2025-39698Sep 5, 2025 · io_uring/futex: ensure io_futex_wait() cleans up properly on failure
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0ff42a32784e0f2cb46a46da8e9f473538c13e1bVendor (CNA)
Linux Linux181feb41f0b268e6288bf9a7b984624d7fe2031dVendor (CNA)
Linux Linux202a3432d21ac060629a760fff3b0a39859da3eaVendor (CNA)
Linux Linux76d2e3890fb169168c73f2e4f8375c7cc24a765eVendor (CNA)
Linux Linux92278ae36935a54e65fef9f8ea8efe7e80481aceVendor (CNA)
Linux Linuxc32e3c71aaa1c1ba05da88605e2ddd493c58794fVendor (CNA)
Linux Linuxf230d40147cc37eb3aef4d50e2e2c06ea73d9a77Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.85.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.41.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records