CVE-2026-89704

Description

A flaw was found in the Linux kernel's nfsd component. The _nfsd_copy_file_range() function incorrectly samples the writeback error cursor after the copy loop. This allows a concurrent write operation to advance the error cursor prematurely. As a result, the system may report that data has been successfully committed even when writeback errors have occurred, leading to silent data loss where clients perceive data as durable when it is not.

Statement

An async NFS server side COPY can miss a writeback error because _nfsd_copy_file_range samples the dst f_wb_err cursor after the copy loop. A concurrent COMMIT or stable WRITE that reuses the same cached struct file can advance the shared writeback error cursor before the COPY worker checks it, making errseq_check report success even though writeback failed. This can make NFSD report the offloaded copy as committed with FILE_SYNC4 and the client may treat the copied data as durable, resulting in silent data loss. For the CVSS the PR:L is selected because the attacker typically needs valid NFS access and write or COPY permission on the exported filesystem. The issue is network reachable from clients that can access the NFSv4.2 server side COPY path, but practical exploitation also depends on concurrent operations and a real writeback failure. Impact is primarily integrity loss rather than kernel crash or privilege escalation.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactLowN/AHigh
Availability ImpactHighN/ANone

Vector

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

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.

Confidentiality,Integrity

Technical Impact: Read Files or Directories; Read Application Data

When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).

Access Control

Technical Impact: Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism

This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.

Frequently Asked Questions

Want to get errata notifications? Sign up here.