CVE-2026-99358

Description

A flaw was found in the Linux kernel's Network File System daemon (nfsd). When encoding an NFSv4 COMPOUND response, the server does not initialize memory padding bytes if a tag length is not aligned to a four-byte boundary. A remote client can exploit this flaw by sending a request with an unaligned tag length, resulting in information disclosure of uninitialized kernel memory in server replies.

Statement

This vulnerability is rated as having a Moderate impact because an unauthenticated network attacker can leak residual kernel memory without directly compromising system stability or integrity. The flaw only affects hosts configured as NFSv4 servers, a role that is not enabled by default in standard Red Hat Enterprise Linux deployments. Furthermore, the exposure is limited to a few stale memory bytes per transaction, significantly reducing the severity compared to broad memory disclosures or code execution flaws.

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

Vector

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

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.