External risk intelligence

Linux Kernel NFS Sequence Reply Buffer Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99362

The vulnerability exists in the Linux kernel's nfsd (NFS server) implementation. While NFS can be exposed to the internet, it is a file-sharing protocol typically restricted to internal, private, or trusted networks via firewalls and access controls. Public-facing deployment of NFS is generally considered a misconfiguration or uncommon practice, making internet exposure unlikely in typical deployments.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in the Linux kernel's NFS server that could potentially allow an attacker to write beyond allocated memory buffers. This could lead to system instability or other unintended consequences. While the technical details involve how replies are handled, the core concern is a memory corruption issue in a core network service.

  • Handles data incorrectly for network file sharing.
  • Important for core Linux network services stability.
  • Confirm if NFS server is in use and exposed.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted SEQUENCE replies to an NFS server. This could lead to a buffer overflow, allowing an attacker to potentially overwrite memory and gain control of the system.

  • Network access is required.
  • Malicious SEQUENCE replies trigger the flaw.
  • Memory corruption could lead to system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to cause a kernel memory read and write out-of-bounds when processing NFS SEQUENCE replies. This could lead to a denial-of-service or potentially allow an attacker to read or modify kernel memory.

  • Kernel memory.
  • Processing of NFS SEQUENCE replies.
  • Denial of service or memory corruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects the Linux kernel's NFS server (nfsd) and could allow an unauthenticated attacker to achieve arbitrary read/write in kernel memory, leading to system compromise. Infrastructure or platform teams are likely responsible for the Linux kernel. The immediate first step is to identify all NFS server instances, determine their network exposure and business criticality, and confirm ownership before planning remediation.

  • Identify NFS server instances and exposure.
  • Confirm accountable system or application owners.
  • Plan remediation based on confirmed risk.

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 nfsd component?

The nfsd, or Network File System daemon, is a core Linux kernel service that enables a server to share directories and files over a network. It allows remote client systems to mount these shared directories as if they were local storage, facilitating centralized file access and data sharing in distributed computing environments.

How does CVE-2026-99362 cause memory issues?

This vulnerability is an out-of-bounds memory error. It occurs because the NFS server fails to properly check if a response buffer has enough space for certain operations. Because the buffer is narrowed incorrectly, the system writes data beyond the allocated memory boundaries, which can corrupt kernel memory.

Do I need specific triggers to set off this bug?

Yes, an attacker must send a specifically crafted NFS SEQUENCE operation to the server. If the server is configured to limit the response size for a session, it creates the condition where the system attempts to copy data into an undersized buffer. Normal, valid file system traffic that does not involve these specific negotiated size limits will not trigger the flaw.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that while the vulnerability is serious, the risk is currently labeled as unlikely. This is because NFS is primarily designed for internal or private networks. If your NFS server is directly exposed to the internet, your risk profile increases; however, such exposure is typically considered an uncommon configuration.

How should I respond to CVE-2026-99362?

Your first step is to locate all systems running the NFS server component within your environment. Once identified, evaluate their network placement to confirm if they are isolated from the internet. Finally, verify the ownership of these systems to coordinate with the appropriate teams for upcoming kernel security updates.

References