---
id: CVE-2025-40342
title: |-
  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…
summary: |-
  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…
severity: high
cvss: 8.8
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
published: '2025-12-09'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T21:10:00.183'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-40342'
references:
  - url: 'https://git.kernel.org/stable/c/25f4bf1f7979a7871974fd36c79d69ff1cf4b446'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/4253e0a4546138a2bf9cb6acf66b32fee677fc7c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/891cdbb162ccdb079cd5228ae43bdeebce8597ad'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9950af4303942081dc8c7a5fdc3688c17c7eb6c0'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a2f7fa75c4a2a07328fa22ccbef461db76790b55'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/de3d91af47bc015031e7721b100a29989f6498a5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e8cde03de8674b05f2c5e0870729049eba517800'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00366
epssPercentile: 0.2875
ingestedAt: '2026-10-14T21:57:04.738Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.