vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2025-40342

nvme-fc: use lock accessing port_state and rport state

HIGH
8.8
CVSS Score
Published: December 9, 2025 at 04:09 AM UTC
Updated: October 14, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because nvme_fc_create_association is not taking a lock to check the port_state and atomically increase the active count on the rport.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel· Linux
90%
4.10e399441de9115cd472b8ace6c517708273ca7997
Vendor states this is fixed in 25f4bf1f7979a7871974fd36c79d69ff1cf4b446 (fixed)
Vendor states this is fixed in 4253e0a4546138a2bf9cb6acf66b32fee677fc7c (fixed)
Vendor states this is fixed in 891cdbb162ccdb079cd5228ae43bdeebce8597ad (fixed)
Vendor states this is fixed in 9950af4303942081dc8c7a5fdc3688c17c7eb6c0 (fixed)
Vendor states this is fixed in a2f7fa75c4a2a07328fa22ccbef461db76790b55 (fixed)
Vendor states this is fixed in de3d91af47bc015031e7721b100a29989f6498a5 (fixed)
Vendor states this is fixed in e8cde03de8674b05f2c5e0870729049eba517800 (fixed)
Vendor states this is fixed in 4.10 (unaffected)
Vendor states this is fixed in 5.10.247 (unaffected)
Vendor states this is fixed in 5.15.197 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.58 (unaffected)
Vendor states this is fixed in 6.17.8 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.117 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (7)

Source: cverecord
https://git.kernel.org/stable/c/de3d91af47bc015031e7721b100a29989f6498a5
Source: cverecord
https://git.kernel.org/stable/c/e8cde03de8674b05f2c5e0870729049eba517800
Source: cverecord
https://git.kernel.org/stable/c/4253e0a4546138a2bf9cb6acf66b32fee677fc7c
Source: cverecord
https://git.kernel.org/stable/c/25f4bf1f7979a7871974fd36c79d69ff1cf4b446
Source: cverecord
https://git.kernel.org/stable/c/9950af4303942081dc8c7a5fdc3688c17c7eb6c0
Source: cverecord
https://git.kernel.org/stable/c/a2f7fa75c4a2a07328fa22ccbef461db76790b55
Source: cverecord
https://git.kernel.org/stable/c/891cdbb162ccdb079cd5228ae43bdeebce8597ad

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card