CVE-2026-90103

Description

A flaw was found in the Linux kernel's NFSv4.2 (Network File System version 4.2) component. A malicious or specially crafted data server can exploit an issue in the LAYOUTSTATS handling, where the send buffer can be exhausted due to an undersized allocation. This can lead to a permanent lock being held, resulting in a Denial of Service (DoS) condition for the affected system.

Statement

A moderate severity flaw was found in the Linux kernel's NFSv4.2 handling of LAYOUTSTATS. The encode_layoutstats_maxsz macro reserves only 256 bytes for the layoutupdate4 body written by the layout driver, but the flexfiles layout driver can emit a record that exceeds this reservation: a data server filehandle of NFS_MAXFHSIZE bytes combined with the per-data-server address, I/O latency, timestamp, and boolean fields pushes the encoded body past the 256-byte budget before the address is encoded at all. Because the filehandle and the address are chosen by the server through LAYOUTGET and GETDEVICEINFO, a malicious or specially crafted data server can drive the encoder past the end of the send buffer. When that happens, xdr_reserve_space() returns NULL while the mirror lock is held, leaving the lock permanently held and resulting in a denial of service on the NFS client. Exploitation requires a client to use an NFSv4.2 mount with pNFS flexfiles layouts served by a malicious or untrusted server, which limits exposure in typical deployments. Red Hat Enterprise Linux 7, 8, 9, and 10 (kernel and kernel-rt), Red Hat In-Vehicle OS, and the Red Hat CoreOS kernels shipped in OpenShift Container Platform 4 are affected; fixes for these streams are currently deferred to a future update, and the residual risk is denial of service limited to clients using pNFS flexfiles layouts against an untrusted server. Red Hat Enterprise Linux 6 is not affected because the vulnerable code is not present in that stream. Red Hat rates this flaw as moderate severity (CVSS 5.5 with a local attack vector), which differs from the upstream CVE record score of 7.5 that assumes a network attack vector.

Mitigation

Mitigation for this issue is either not available or the currently available options do not 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.5N/A7.5
Attack VectorLocalN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity,Availability,Confidentiality

Technical Impact: DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands; Read Memory; Modify Memory

If the incorrect calculation is used in the context of memory allocation, then the software may create a buffer that is smaller or larger than expected. If the allocated buffer is smaller than expected, this could lead to an out-of-bounds read or write (CWE-119), possibly causing a crash, allowing arbitrary code execution, or exposing sensitive data.

Frequently Asked Questions

Want to get errata notifications? Sign up here.