External risk intelligence

Linux Kernel XFS pNFS Commit Flaw Leads to Filesystem Corruption

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-99679

This vulnerability exists within the Linux kernel's XFS filesystem handling related to pNFS (Parallel NFS) layout commits. Such low-level filesystem operations are deep internal kernel functions not exposed directly to the public internet. While NFS may be network-accessible, the specific code path for XFS layout validation is not an internet-facing service or interface.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability in the Linux kernel's XFS filesystem could allow an attacker to commit invalid data ranges, potentially leading to data corruption or system instability. The main concern is to confirm if your environment utilizes this specific Linux kernel component and is exposed to the described conditions.

  • Filesystem commits can be corrupted.
  • Critical Linux kernel function is impacted.
  • Confirm if this impacts your Linux systems.

Attack Path

How an attacker could exploit the issue

An attacker could trigger this vulnerability by sending a specially crafted pNFS LAYOUTCOMMIT request to a Linux system. This request targets the XFS filesystem's handling of file extents, specifically when dealing with unwritten data ranges. By manipulating these extents, an attacker could cause the filesystem to allocate blocks incorrectly, potentially leading to system instability or the exposure of stale data.

  • No authentication or special privileges needed.
  • Malicious pNFS LAYOUTCOMMIT request.
  • Filesystem instability or stale data exposure.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in the Linux kernel's XFS filesystem could allow a client to commit a file hole during a LAYOUTCOMMIT. This may result in the XFS filesystem shutting down or exposing stale data when supported by the advisory's configuration.

  • Filesystem integrity and data confidentiality.
  • Client commits invalid range during LAYOUTCOMMIT.
  • Filesystem instability or exposure of stale data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides in the Linux kernel's XFS filesystem, specifically affecting pNFS layout commits. Identifying affected systems involves determining if pNFS is in use and if the XFS filesystem is exposed. Infrastructure or platform teams are likely responsible for the kernel and filesystem, with security teams needing to confirm exposure and critical impact before planning remediation with relevant system owners.

  • Kernel and filesystem teams own remediation.
  • Verify pNFS and XFS usage and exposure.
  • Plan updates during maintenance windows.

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 XFS component affected by CVE-2026-99679?

XFS is a high-performance 64-bit journaling file system used extensively in Linux environments for large-scale data storage. This vulnerability specifically impacts how the kernel handles pNFS (Parallel NFS) layout commits. When a system acts as an NFS server using XFS, it must manage file layouts—the mapping of file data to disk blocks. The issue lies in the validation logic for these mapping requests, which is a specialized task for managing distributed file access over a network.

How does this vulnerability manifest as a security weakness?

This flaw involves an improper input validation weakness. When a pNFS client sends a LAYOUTCOMMIT request, the kernel fails to verify if the requested range actually contains valid data blocks. Because it accepts a 'hole' or empty space in the file, the system may incorrectly allocate physical storage or expose remnants of previous data. This logic error transforms a standard storage management request into a mechanism that can destabilize the file system or compromise data confidentiality.

What triggers this XFS filesystem issue?

An attacker must send a specially crafted pNFS LAYOUTCOMMIT request to the target system. The bug is triggered when this request specifies a range that lacks allocated blocks. It is important to note that normal, correctly formatted storage operations or file access that does not involve pNFS layout manipulation will not trigger this vulnerability. The flaw is strictly tied to the specific interaction between pNFS client communication and the XFS internal block allocation logic.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates that exploitation is very unlikely for most environments. While the NFS service itself might be network-accessible, the vulnerable XFS code path operates deep within the kernel's internal file system handling. This is not an internet-facing interface; it requires specific, low-level integration between the pNFS protocol and the XFS architecture. Most typical internet-facing services do not provide the necessary access to trigger this kernel-level process.

How should I respond to CVE-2026-99679?

Your first step is to determine if your Linux systems utilize pNFS in conjunction with XFS. If you are not using pNFS, this vulnerability is not applicable to your environment. For systems that do use these technologies, coordinate with your infrastructure or kernel management teams to verify your current Linux kernel version. Plan to incorporate the necessary kernel updates during your regular maintenance cycles to resolve the validation gap in the XFS file system driver.

References