CVE-2026-99677

Description

A flaw was found in the Linux kernel's XFS file system. When handling Parallel Network File System (pNFS) layout requests, the kernel does not properly validate or clamp requested file offset and length boundaries. A remote attacker with access to an exported file share could send a crafted layout request with extreme values, causing integer wrapping and allowing a read layout to be constructed from uninitialized memory mappings. This could result in information disclosure or a Denial of Service (DoS).

Statement

Red Hat has rated this vulnerability as having Important severity because a remote authenticated client can induce uninitialized memory access or system panics on a server hosting exported storage, presenting a broader network blast radius than local-only flaws. Exploitation requires the host to operate as an NFS server exporting an XFS filesystem with Parallel NFS (pNFS) layout operations enabled, a configuration that is not active by default in standard Red Hat Enterprise Linux installations. Systems that do not export XFS shares via pNFS or do not run NFS server services are unaffected by this flaw.

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.1N/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 ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

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

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.