CVE-2025-40261

Description

A flaw was found in the Linux kernel's NVMe over Fibre Channel (NVMe-FC) storage driver. A race condition during controller teardown allows error-handling tasks to remain queued or run after the associated controller data structure has been freed. An attacker or malfunctioning endpoint on the storage fabric could exploit this flaw by provoking input/output (I/O) errors while a controller is being removed. This can cause memory corruption and a system crash, resulting in a denial of service (DoS).

Statement

A race in the NVMe FC controller delete path can allow ioerr_work to be queued after cancel_work_sync has already returned. If the nvme_fc_ctrl object is then freed while the work item is still queued or running, the workqueue can operate on stale memory and trigger list corruption or a kernel BUG. For the CVSS the PR:N is used for the paranoid network adjacent model because a malicious or faulty FC target or fabric endpoint may provoke I/O errors without needing a local account on the host. The attack is not Internet remote and requires access to the Fibre Channel storage fabric or a trusted storage path. Impact is at least denial of service via kernel crash. In the paranoid case, limited confidentiality or integrity impact is kept because the bug has a plausible use after free and list corruption pattern, but no clear arbitrary write primitive is shown.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/A9.8
Attack VectorAdjacent NetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.