External risk intelligence

Linux Kernel nvmet-fc Association Deletion Double Schedule Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-40343

This vulnerability exists in the Linux kernel nvmet-fc (NVMe over Fibre Channel) subsystem. NVMe over Fibre Channel is a storage networking protocol typically used in isolated, high-performance data center storage area networks (SANs) and is not designed for or deployed on the public internet.

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 advisory addresses a vulnerability in the Linux kernel's storage subsystem that, if exploited, could allow for critical impacts to system availability and data integrity. The issue arises from a flaw in how port shutdowns are handled, potentially leading to the improper deletion of data associations. While the main concern is confirming relevance and exposure, the potential for significant system disruption warrants attention.

  • Improper port shutdown could delete data associations.
  • It enables a critical remote code execution flaw.
  • Confirm relevance and scope of affected systems.

Attack Path

How an attacker could exploit the issue

An attacker could trigger this vulnerability by interacting with the Linux kernel's nvmet-fc subsystem, potentially through the configfs interface. This interaction involves forcefully shutting down a port, which can lead to a race condition where association deletion is scheduled twice. If successful, this could allow an attacker to gain unauthorized access, modify data, or disrupt services.

  • Requires interaction with the kernel's storage subsystem.
  • Triggered by forceful port shutdown race condition.
  • Allows unauthorized access, data modification, or disruption.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in the Linux kernel's nvmet-fc subsystem could allow a double-free condition when a port is forcefully shut down. This may lead to system instability or crashes.

  • Kernel association data could be affected.
  • Double-free can occur during port shutdown.
  • System instability or crashes may result.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides in the Linux kernel's nvmet-fc subsystem, impacting storage area networks. Identifying and securing these specialized environments falls to infrastructure and platform teams, in coordination with network and security operations. The initial priority is to confirm the presence of the affected technology within controlled, high-performance storage networks, assess its reachability and criticality, and then plan remediation in alignment with established maintenance windows.

  • Infrastructure and platform teams own.
  • Verify affected storage network reachability.
  • Plan remediation 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 nvmet-fc subsystem?

The nvmet-fc component enables NVMe over Fibre Channel, a specialized protocol that allows servers to communicate with high-performance storage devices. It is a critical part of the Linux storage stack, primarily used in data center Storage Area Networks (SANs) to handle high-speed data traffic between hosts and enterprise-grade storage arrays.

What kind of vulnerability is CVE-2025-40343?

This CVE represents a race condition weakness. In plain terms, the software tries to perform the same deletion task twice because it lacks a proper way to track if a task is already underway. This can lead to memory errors, potentially causing the system to crash or behave unexpectedly when managing storage connections.

How is this race condition triggered?

An attacker must be able to interact with the system's configuration interface to forcefully shut down a storage port. The vulnerability does not trigger during normal operation or standard data traffic; it specifically requires the sequence of events involved in shutting down an active port to fail due to the timing flaw.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that this vulnerability exists in specialized storage networking protocols. Because NVMe over Fibre Channel is designed for isolated, high-performance data center networks and not for the public internet, it is very unlikely that your storage infrastructure is exposed to external attacks.

How should I respond to this advisory?

Your first step is to work with your platform and infrastructure teams to identify if your servers utilize the nvmet-fc subsystem. If confirmed, assess the criticality of those storage environments. Since remediation involves kernel-level changes, plan to apply official updates during your next scheduled maintenance window for infrastructure components.

References