CVE-2026-99358 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

nfsd: zero NFSv4 COMPOUND tag padding

nfs4svc_encode_compoundres() copies the tag bytes into reserved XDR space and skips directly to the aligned end of the field. xdr_reserve_space() rounds the reservation up but does not initialize the padding bytes.

A remote client can choose a tag length that is not a multiple of four, causing one to three stale bytes from the response page to be returned in the COMPOUND reply.

Use xdr_encode_opaque_fixed() to copy the tag and clear its XDR padding.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability identified as CVE-2024-something (specifically related to nfsd NFSv4 COMPOUND tag handling) represents a classic memory safety issue within the Linux kernel's Network File System server implementation. The core of this flaw lies in how the function nfs4svc_encode_compoundres handles data serialization for NFS version 4 compound operations. When encoding the response, the code copies the client-supplied tag bytes into reserved XDR (External Data Representation) space and then skips directly to the aligned end of that field. While xdr_reserve_space correctly rounds up the reservation size to maintain four-byte alignment required by the protocol, it does not initialize or clear the padding bytes added during this rounding process. This oversight means that any memory allocated for these padding areas retains its previous state from prior operations rather than being zeroed out as expected in secure coding practices.

From a technical perspective, this is an information disclosure vulnerability classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor and more specifically CWE-1341: Use of Hard-coded or Uninitialized Memory for Padding Bytes. The operational impact arises when a remote client submits a tag length that is not a multiple of four bytes. In such cases, the XDR encoding process leaves one to three padding bytes uninitialized. Because these bytes are part of the response page which may have been used in previous network operations, they can contain stale data from prior requests or responses. Consequently, when the server sends back the COMPOUND reply, it inadvertently leaks this residual memory content alongside the legitimate tag and other protocol fields. This constitutes a side-channel information leak that could potentially expose sensitive kernel memory contents to an unauthenticated remote attacker.

The severity of this vulnerability is influenced by its potential for exploitation in network-facing services. Although NFSv4 requires authentication in most production environments, the ability to read uninitialized kernel stack or heap data can aid attackers in bypassing ASLR (Address Space Layout Randomization) or discovering other memory corruption bugs within the same process space. This aligns with ATT&CK technique T1082: System Information Discovery, where an adversary gathers information about the target system through network protocols. The lack of proper initialization violates fundamental principles of secure data handling in C-based systems, particularly when dealing with variable-length fields that require padding for protocol compliance.

Mitigation strategies primarily involve applying the kernel patch provided by Linux distribution maintainers which replaces the manual copying and skipping logic with xdr_encode_opaque_fixed(). This function ensures that both the tag bytes are correctly copied and the necessary XDR padding is explicitly cleared to zero before transmission. Administrators should ensure their systems are updated to include this fix, as it addresses the root cause by enforcing strict memory initialization for all protocol fields regardless of length alignment requirements. Additionally, implementing network segmentation and restricting NFS server access to trusted networks can reduce the attack surface while patches are being deployed across infrastructure assets.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00201

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!