External risk intelligence

Linux Kernel NFSv4 Session Slot Unhandled Replay Race

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99366

The vulnerability exists within the Linux kernel's NFS server (nfsd) implementation. While NFS is a network-based protocol and potentially reachable over a network, it is typically deployed within internal, trusted local area networks rather than being directly exposed to the public internet. Internet-facing deployment of NFS is generally discouraged due to security risks, making external reachability possible but not the common norm.

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 vulnerability in the Linux kernel's NFS server could allow for system instability or crashes by improperly handling network requests. At a high level, this means that if this specific function within the kernel is triggered in a certain way, it could lead to an unpredictable and severe failure of the server.

  • Kernel function doesn't correctly track requests.
  • Affects stability and could crash servers.
  • Confirm relevance and exposure for internal systems.

Attack Path

How an attacker could exploit the issue

An attacker could reach this vulnerability by sending specially crafted network requests to a Linux system running the NFS server. This exposure allows an attacker to send multiple replay requests for the same NFS session simultaneously. When these requests are processed, the system may incorrectly handle session slot management, leading to a kernel NULL pointer dereference or a use-after-free write.

  • Requires network access to the NFS server.
  • Triggered by concurrent NFS session replays.
  • Risk of system crash and data corruption.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in the Linux kernel's NFS server could allow multiple concurrent replays of NFS operations. When supported by the advisory, this could lead to a NULL pointer dereference, causing a kernel panic and system instability. In some configurations, this could also lead to a use-after-free write.

  • Kernel data integrity could be affected.
  • Concurrent NFS operations could trigger the issue.
  • System instability or data corruption may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Linux kernel's NFS server (nfsd) is impacted by this vulnerability. In a real-world scenario, the platform or infrastructure team responsible for the NFS service and the Linux operating system would likely own this issue. The initial actions should focus on identifying all NFS server instances, assessing their exposure and criticality, and then coordinating with the relevant teams for remediation.

  • Identify NFS server instances.
  • Verify NFS server exposure and criticality.
  • Plan and execute remediation.

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 role of the Linux kernel nfsd component?

The nfsd component enables a Linux system to operate as an NFS server. It provides the core functionality for remote clients to access, share, and manage distributed storage over a network, acting as the foundation for networked file services.

Why does a race condition occur in the nfsd session slot management?

The issue stems from a failure to correctly identify cached reply operations. Because the kernel fails to set the slot usage flag during a replay, multiple concurrent requests can attempt to modify the same session slot simultaneously, leading to memory corruption or invalid pointer dereferences.

How can concurrent NFS replays trigger a kernel panic?

When the system fails to track slot ownership, overlapping replays may trigger a NULL pointer dereference or a use-after-free write. This occurs because the kernel may free a slot while another operation is still accessing its credentials or session data, causing a fatal exception that halts the kernel.

Is this NFS vulnerability relevant to my network environment?

The Halo Surface Signal classifies this as a possible risk. While the vulnerability requires network access to the NFS server, such services are typically restricted to internal, trusted segments. External exposure is possible but is not the common deployment pattern.

How should administrators respond to this NFS kernel issue?

Infrastructure teams should prioritize identifying all active NFS server instances within the environment. Once assets are mapped, evaluate the criticality of each server to plan for necessary kernel updates, ensuring the service remains stable and protected against concurrent request processing errors.

References