External risk intelligence

Linux Kernel NFSD SETXATTR Buffer Copy Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-99370

This vulnerability exists within the Linux kernel NFSD (NFS server) component. While NFS services are often deployed within internal, restricted networks, they can be exposed to the public internet in specific enterprise or cloud configurations. As there is no inherent design requiring public exposure for typical file sharing operations, it is classified as possible.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability in the Linux kernel's NFS server could allow unauthorized access or modification of data by incorrectly handling data segments. It impacts how file attributes are set, potentially leading to data integrity issues or system instability if exploited. The main concern is confirming relevance and exposure to your environment.

  • Incorrectly set file attributes can occur.
  • NFS server data handling flaw exposed.
  • Confirm if your NFS servers are affected.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network requests to a vulnerable NFS server. The issue lies in how the server handles certain data when processing extended attributes, potentially leading to incorrect data being written. This could result in the server becoming unstable or allowing unauthorized modifications.

  • Unauthenticated network access required.
  • Malicious data triggers incorrect file attribute writes.
  • Potential for denial of service or data corruption.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an issue in the Linux kernel's NFS server could lead to incorrect data being written to extended attributes, potentially affecting file integrity and system stability.

  • File extended attribute data.
  • Incorrect data copied from buffer segments.
  • File integrity or system stability.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's NFSD component requires immediate attention from infrastructure and platform teams responsible for managing NFS services. The first practical step is to identify all NFS server instances, determine their exposure (internal or external), confirm their business criticality, and then prioritize remediation actions, which may involve vendor coordination or applying kernel updates.

  • Infrastructure and platform teams own resolution.
  • Verify NFS server reachability and criticality.
  • Plan kernel updates or vendor coordination.

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?

NFSD, or the NFS Server, is a component of the Linux kernel that enables a system to act as a file server. It allows other computers on a network to access, read, and write files as if they were stored locally on their own drives. It is widely used in enterprise environments to facilitate centralized file storage, shared workspaces, and distributed data access across server clusters and workstations.

What does this CVE-2026-99370 vulnerability mean?

This vulnerability is an input validation error related to how the kernel manages memory buffers. When the NFS server processes extended file attributes, it fails to correctly locate and copy all segments of the data sent by a client. Because it misinterprets the memory layout, the system may write the wrong information to the file attributes, which can corrupt data integrity or cause the server to crash.

How can an attacker trigger this bug?

An attacker triggers the vulnerability by sending a specially crafted network request to the NFS server. This request must specifically target the extended attribute functionality. Simply accessing files or standard network traffic will not trigger the bug; the system is only at risk when it attempts to decode these specific, malformed attribute-related data packets.

Do I need to worry if my NFS server is internal?

According to Halo Surface Signal, this vulnerability is classified as 'Possible' for most users. While NFS is typically kept on private, restricted networks, some cloud or enterprise setups do expose these services to the public internet. You should evaluate your network perimeter to see if your NFS infrastructure is reachable from outside your organization, as public exposure significantly increases the potential risk.

What should I do first to address this?

The immediate priority is to conduct an inventory of your environment to locate all running NFS server instances. Once identified, verify their network reachability and business importance. After assessing which systems are exposed or critical, coordinate with your infrastructure team to plan for kernel updates provided by your distribution vendor, which will contain the necessary code fixes.

References