Skip to main content

Linux Kernel CVE-2025-40171

HIGH
2025-11-12 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.5
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
3.1 LOW

FC-fabric adjacent reach (AV:A), no auth in the FC transport (PR:N), race-dependent multiple-in-flight trigger (AC:H), and a gradual resource leak giving limited availability impact (A:L).

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
4.0 AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
SUSE
5.3 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

8
Analysis Updated
Jul 30, 2026 - 08:44 vuln.today
v4 (cvss_changed)
Analysis Updated
Jul 30, 2026 - 08:43 vuln.today
v3 (cvss_changed)
Analysis Updated
Jul 30, 2026 - 08:43 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Jul 30, 2026 - 06:37 vuln.today
cvss_changed
CVSS changed
Jul 30, 2026 - 06:37 NVD
7.5 (HIGH)
Patch released
Mar 28, 2026 - 19:31 nvd
Patch available
Analysis Generated
Mar 28, 2026 - 19:21 vuln.today
CVE Published
Nov 12, 2025 - 11:15 nvd
N/A

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

nvmet-fc: move lsop put work to nvmet_fc_ls_req_op

It’s possible for more than one async command to be in flight from __nvmet_fc_send_ls_req. For each command, a tgtport reference is taken.

In the current code, only one put work item is queued at a time, which results in a leaked reference.

To fix this, move the work item to the nvmet_fc_ls_req_op struct, which already tracks all resources related to the command.

AnalysisAI

Resource exhaustion in the Linux kernel's NVMe-oF Fibre Channel target driver (nvmet-fc) stems from a reference-counting error in Link Service request handling: when multiple asynchronous LS commands are in flight from __nvmet_fc_send_ls_req, each takes a tgtport reference but only a single put-work item is queued, leaking the surplus references. Systems acting as NVMe-over-Fabrics FC targets are affected, and the leaked references prevent proper teardown of the target port, degrading availability over time. This is a defensive kernel hardening fix with no public exploit identified at time of analysis and a very low EPSS (0.05%).

Technical ContextAI

NVMe over Fabrics (NVMe-oF) allows NVMe storage commands to traverse a network transport; nvmet-fc is the in-kernel target-side driver implementing the Fibre Channel transport. During connection setup and management, the target issues Link Service (LS) requests via __nvmet_fc_send_ls_req, and each outstanding async command holds a reference on the tgtport object to keep it alive for the command's lifetime. The bug is a reference-count / resource leak (functionally CWE-911 'Improper Update of Reference Count' / CWE-401 'Missing Release of Memory'): the cleanup work item was shared/global so only one queued put ran even when several commands were concurrently in flight, orphaning the extra references. The fix relocates the put-work item into the per-command nvmet_fc_ls_req_op structure, which already owns all resources for a single command, guaranteeing one put per reference taken. The upstream CWE field is unpopulated (N/A).

Affected ProductsAI

The affected product is the Linux kernel, specifically the nvmet-fc NVMe-over-Fabrics Fibre Channel target driver. Exact affected version ranges are not enumerated in the provided data (NVD CPE strings were not supplied); the six git.kernel.org stable commit references (e.g. 060ecc81240ef9d60d9485a3a5eb55a0d6e7a25c and db5a5406fb7e5337a074385c7a3e53c77f2c1bd3) indicate the fix was backported across multiple stable branches. Distribution exposure is confirmed for Ubuntu via advisories USN-8126-1 (https://ubuntu.com/security/notices/USN-8126-1) and USN-8125-1 (https://ubuntu.com/security/notices/USN-8125-1), which enumerate the specific Ubuntu kernel package versions fixed. Only systems built with CONFIG_NVME_TARGET_FC and actively configured as FC targets exercise the vulnerable path.

RemediationAI

Upstream fix available (multiple stable-tree commits); update to a distribution kernel that incorporates the patch. For Ubuntu, apply the kernel updates specified in USN-8126-1 (https://ubuntu.com/security/notices/USN-8126-1) and USN-8125-1 (https://ubuntu.com/security/notices/USN-8125-1) and reboot; for mainline/stable users, take a kernel containing the referenced commits (https://git.kernel.org/stable/c/db5a5406fb7e5337a074385c7a3e53c77f2c1bd3 and the related backports). If patching must be deferred, the practical compensating control is to avoid or disable the NVMe-oF FC target role on systems that do not require it - do not load/enable the nvmet-fc target configuration (blacklist the nvmet_fc module or refrain from binding FC target ports via configfs), which fully removes exposure at the cost of that host being unable to serve NVMe storage over Fibre Channel. Restricting FC fabric zoning so only trusted initiators can reach the target reduces who can drive LS traffic, at the cost of tighter SAN administration.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/hpc/warewulf4-x86_64/sle-hpc-node:latest Image SLES15-SP6 Image SLES15-SP6-BYOS Image SLES15-SP6-BYOS-Azure Image SLES15-SP6-BYOS-EC2 Image SLES15-SP6-BYOS-GCE Image SLES15-SP6-CHOST-BYOS Image SLES15-SP6-CHOST-BYOS-Aliyun Image SLES15-SP6-CHOST-BYOS-Azure Image SLES15-SP6-CHOST-BYOS-EC2 Image SLES15-SP6-CHOST-BYOS-GCE Image SLES15-SP6-CHOST-BYOS-GDC Image SLES15-SP6-CHOST-BYOS-SAP-CCloud Image SLES15-SP6-EC2 Image SLES15-SP6-EC2-ECS-HVM Image SLES15-SP6-GCE Image SLES15-SP6-HPC-BYOS Image SLES15-SP6-HPC-BYOS-Azure Image SLES15-SP6-HPC-BYOS-EC2 Image SLES15-SP6-HPC-BYOS-GCE Image SLES15-SP6-HPC-EC2 Image SLES15-SP6-HPC-GCE Image SLES15-SP6-Hardened-BYOS Image SLES15-SP6-Hardened-BYOS-Azure Image SLES15-SP6-Hardened-BYOS-EC2 Image SLES15-SP6-Hardened-BYOS-GCE Image SLES15-SP6-SAP Image SLES15-SP6-SAP-Azure Image SLES15-SP6-SAP-EC2 Image SLES15-SP6-SAP-GCE Image SLES15-SP6-SAPCAL Image SLES15-SP6-SAPCAL-Azure Image SLES15-SP6-SAPCAL-EC2 Image SLES15-SP6-SAPCAL-GCE Affected
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.1/baremetal-os-container:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.95 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.80 Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.114 Container suse/sl-micro/6.1/kvm-os-container:2.2.1-5.82 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.116 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.55 Affected

Share

CVE-2025-40171 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy