External risk intelligence

Linux Kernel Lockd Use-After-Free Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99513

The vulnerability exists within the Linux kernel lockd component, which manages Network Lock Manager (NLM) tasks for NFS. While NLM operates over the network, it is typically deployed within trusted local area networks or restricted server-to-server environments. Direct public internet exposure of NFS/lockd services is considered uncommon and contrary to standard security best practices for file sharing protocols.

Use After Free

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 critical vulnerability in the Linux kernel's network lock manager could allow for system instability or crashes. While impactful, its exploitation is considered unlikely given typical deployment scenarios.

  • Kernel issue may cause system instability.
  • Consider if your network lock manager is exposed.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit a use-after-free vulnerability in the Linux kernel's lockd component. This occurs when the NFS client attempts to unmount an NFS filesystem while a lock request is still being processed. By manipulating the timing of these operations, an attacker could cause the kernel to access memory that has already been freed, potentially leading to a system crash or code execution.

  • Network access required for exposure.
  • Unmounting NFS during lock requests triggers.
  • Potential for system instability or control.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could affect the integrity and availability of system services when the NFS client attempts to unmount an NFS filesystem while a lock request is still blocked. This scenario might lead to unexpected behavior or crashes within the lockd component of the Linux kernel.

  • System services related to NFS locking.
  • Unmounting NFS while locks are blocked.
  • Potential service instability or crashes.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's `lockd` component affects how network lock manager requests are handled, potentially leading to use-after-free errors. Ownership likely falls to infrastructure or platform teams managing Linux systems, with the first practical step being to identify all systems running the affected kernel and assess their exposure, particularly if they host NFS services.

  • Linux infrastructure or platform teams.
  • Verify NFS and lockd service exposure.
  • Plan for kernel updates or system restarts.

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

Lockd is a core component of the Linux kernel responsible for the Network Lock Manager (NLM) protocol. It enables file locking across a network, allowing multiple clients to safely access the same files on a shared Network File System (NFS). It ensures data consistency by managing which client can read or write to a specific file at any given time.

What does this CVE-2026-99513 vulnerability mean?

This is a use-after-free vulnerability, which is a memory management flaw. It occurs when a program continues to use a pointer to a memory location after that memory has been deallocated or freed. In this specific case, the kernel improperly handles memory associated with blocked lock requests, which can lead to system instability or unpredictable behavior.

How is this vulnerability triggered?

The flaw is triggered during a specific sequence of NFS operations. It occurs when an NFS filesystem is unmounted while a file lock request is still actively blocked and waiting to be processed. Normal system activity that does not involve this specific race condition between unmounting and blocked lock processing does not trigger the vulnerability.

Do I need to worry about this vulnerability?

According to Halo Surface Signal, this vulnerability is unlikely to be triggered in many environments. While the NFS lockd service operates over the network, it is typically restricted to trusted local networks or private server-to-server connections. You should be most concerned if your infrastructure exposes NFS services directly to the public internet, which deviates from standard security practices.

How should I respond to CVE-2026-99513?

The first step is to identify all systems in your environment that are running the affected Linux kernel and utilize NFS services. Once identified, prioritize these systems for kernel updates provided by your distribution. Because this involves a core kernel component, plan for appropriate testing and scheduled system restarts to apply the patches effectively.

References