External risk intelligence

Linux Kernel SUNRPC Incorrect Octet Crediting Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99356

The vulnerability resides in the Linux kernel SUNRPC (RPC over TCP) implementation, which handles network-facing traffic. As a core component of network communication services and file sharing protocols (such as NFS) that are commonly exposed to network or internet segments to facilitate remote service operations, this interface is frequently reachable in typical server and infrastructure deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

The Linux kernel has a resolved vulnerability in its SUNRPC component that handles network communication. This issue could potentially allow unauthenticated network access, leading to significant system compromise. The main concern at this time is confirming relevance and exposure to our environment.

  • RPC communication data handling flaw.
  • Potential for broad, unauthenticated network impact.
  • Verify if our systems use affected RPC services.

Attack Path

How an attacker could exploit the issue

An attacker could send specially crafted network packets to a vulnerable Linux kernel that is processing RPC over TCP. This could cause the system to mismanage received data, leading to unexpected behavior.

  • Requires network access.
  • Triggers on receiving malformed data.
  • Leads to data corruption and crashes.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in the Linux kernel's SUNRPC implementation could allow an attacker to manipulate data streams. This occurs when the system incorrectly credits octets for RPC traffic, leading to the assembly of messages from unreceived data. This can happen when a conforming client interacts with a system that does not have a rekey path for kTLS, potentially causing issues with message integrity.

  • RPC stream data integrity could be compromised.
  • Incorrect octet crediting may occur during data reception.
  • Maliciously crafted messages could be processed.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's SUNRPC component affects core networking and file-sharing services. Infrastructure and platform teams are likely responsible for managing the kernel, while network and security teams should focus on exposure and access controls. The first step is to identify all systems running the affected kernel version, determine their network reachability and business criticality, and then confirm the accountable owner for remediation planning.

  • Kernel and platform teams own remediation.
  • Verify network exposure and criticality first.
  • Plan maintenance for kernel updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Linux kernel SUNRPC component?

SUNRPC stands for Sun Remote Procedure Call. It is a core networking layer in the Linux kernel that facilitates communication between clients and servers. It is essential for distributed services, most notably the Network File System (NFS), which allows systems to share files and resources across a network.

How does CVE-2026-99356 impact data handling?

This vulnerability involves an incorrect calculation where the kernel credits data bytes to a stream that were never actually received. Because the system incorrectly advances its internal record of the data stream, it may assemble messages using stale or uninitialized memory, leading to data integrity issues or system instability.

When does this vulnerability trigger?

The flaw triggers when the kernel processes specific network traffic through its RPC-over-TCP implementation, particularly involving kTLS records that are not alerts. It does not trigger for standard, correctly handled RPC traffic; it specifically manifests during interactions where the system is forced to handle certain record types without a proper rekey path.

Do I need to worry about this if my server is internal?

Halo Surface Signal notes that since this involves core network services and protocols like NFS, it is often reachable across infrastructure segments. Even if a server is not directly on the public internet, any system exposed to broader internal network segments where RPC traffic flows should be evaluated for potential risk.

How do I start addressing CVE-2026-99356?

Your first step is to audit your environment to identify systems running the affected Linux kernel. Once identified, prioritize these based on their business criticality and network reachability. Coordinate with your platform or kernel engineering teams to plan for the necessary kernel updates provided by your distribution vendor.

References