CVE-2026-89677

Description

A flaw was found in the Linux kernel's Network File System Daemon (nfsd). When creating files, the dentry_create() function could return an unexpected directory entry (dentry). This could lead to a previously stored dentry being prematurely freed and then used again, potentially causing memory corruption or a denial of service (DoS) due to an invalid memory access.

Statement

An NFS server use-after-free can occur in nfsd4_create_file because fh_compose may store a filehandle for a dentry before the final dentry is known. If dentry_create returns a different dentry than the original child, the previously stored child can be freed and later dereferenced through the response filehandle path. A remote NFS client with create or open access to an affected export can potentially trigger this through NFSv4 create/open handling, especially in unusual setups such as NFS re-export where dentry aliasing can occur. For the CVSS the PR:L is used because reliable triggering typically requires valid low privilege access to an exported filesystem with permission to create or open files. The issue is network reachable through nfsd, but AC:H is used because the described condition is hypothetical and depends on specific filesystem and dcache behavior. Impact is at least remote denial of service via kernel crash and in the paranoid case may include confidentiality and integrity impact due to the use-after-free class.

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 Score7.5N/A9.8
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.