CVE-2026-99370

Description

A flaw was found in the Linux kernel's Network File System daemon (NFSD). This vulnerability can lead to data corruption when the server processes requests to set extended attributes (SETXATTR). Due to improper handling of multi-segment External Data Representation (XDR) buffers, the service fails to correctly assemble incoming data and copies incorrect bytes. A remote client can exploit this flaw by sending a crafted request, resulting in corrupted or unintended attribute values being written to the filesystem.

Statement

This vulnerability is rated as having Moderate severity because exploitation requires an authenticated client with permissions to modify extended attributes on an active NFS export, and the impact is restricted to corrupted or leaked attribute metadata rather than system compromise. The in-kernel NFS server daemon is not enabled by default on standard Red Hat Enterprise Linux installations, limiting exposure to hosts explicitly configured as NFS file servers. Additionally, the flaw only affects environments exporting shares with NFSv4.2 protocol support enabled.

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.4N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.