External risk intelligence

Linux Kernel NFSd Use-After-Free Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99310

This vulnerability exists within the Linux kernel nfsd (NFS server) component. While NFS is a network service, it is typically deployed within internal, trusted local area networks rather than directly exposed to the public internet. Consequently, while reachability from the internet is technically possible in misconfigured or edge cases, common deployment patterns generally isolate NFS traffic from public access.

Use After Free

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This Linux kernel vulnerability in the NFS server could allow an attacker to exploit a use-after-free condition, potentially leading to system instability or compromise. The main concern is confirming relevance and exposure within your environment.

  • NFS server flaw can cause system instability.
  • This issue impacts core Linux network services.
  • Confirm if your NFS service is exposed.

Attack Path

How an attacker could exploit the issue

An attacker could reach the vulnerable code in the Linux kernel's NFS server by sending a specially crafted request. This occurs when the server is handling client identification, and a race condition allows an attacker to trigger a use-after-free flaw, potentially leading to system instability or code execution.

  • Requires network access.
  • Triggered by concurrent network requests.
  • Risk of system crash or control.

Live Threat

Current exploitation, exposure, and threat context

The Linux kernel's NFS server (nfsd) could be vulnerable when handling concurrent `EXCHANGE_ID` operations. This might allow an attacker to exploit a use-after-free condition, potentially leading to system instability or unauthorized access.

  • Kernel memory integrity.
  • Concurrent NFS operations.
  • System instability or unauthorized access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's NFS server component, specifically within `client_has_openowners()`, could lead to a use-after-free condition when handling `nfsd4_exchange_id`. Given that NFS is often an internal service, the first step is to identify all instances of the affected Linux kernel component, confirm their network reachability and business criticality, and then assign ownership for remediation planning based on this assessment.

  • Identify affected Linux kernel instances.
  • Verify network exposure and business criticality.
  • Plan remediation based on risk assessment.

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 server, is a core kernel component that allows a Linux system to share files and directories with other computers over a network. It acts as the host side of a protocol used widely in enterprise environments for centralized data storage, enabling client machines to access and manage files as if they were stored locally on their own drives.

What does this use-after-free vulnerability mean?

A use-after-free is a memory safety issue where a program continues to use a pointer to a memory location after that memory has been freed or deleted. In CVE-2026-99310, the flaw occurs because the server lacks a specific lock while checking client information. This allows a race condition where the server might try to access a piece of data that was already removed, potentially crashing the service or causing unpredictable behavior.

How is this CVE-2026-99310 vulnerability triggered?

The flaw is triggered during the server's management of client identification requests, specifically when processing concurrent EXCHANGE_ID operations. It requires a precise timing conflict between these requests. Simply having an NFS server enabled does not automatically trigger the issue; it requires specific, simultaneous network traffic that interferes with the server's internal memory management.

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

According to Halo Surface Signal, NFS is typically deployed within protected, internal local area networks rather than directly on the public internet. While you should still prioritize patching, the risk is generally lower for services not exposed to external traffic. If your NFS infrastructure is segmented and limited to trusted internal users, the likelihood of an external attacker reaching this code is significantly reduced.

How should I respond to CVE-2026-99310?

Start by identifying which of your systems are running the affected Linux kernel NFS server. Assess the network reachability of these instances to determine if they are exposed to untrusted traffic. Once you have a clear inventory, prioritize those systems for kernel updates based on their business criticality and exposure level, following your standard patch management process.

References