---
id: CVE-2025-40343
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvmet-fc: avoid scheduling association deletion twice

  When forcefully shutting down a port via the configfs interface,
  nvmet_port_subsys_drop_link() first calls nvmet_…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvmet-fc: avoid scheduling association deletion twice

  When forcefully shutting down a port via the configfs interface,
  nvmet_port_subsys_drop_link() first calls nvmet_…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/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-40343'
references:
  - url: 'https://git.kernel.org/stable/c/04d17540ef51e2c291eb863ca87fd332259b2d40'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2f4852db87e25d4e226b25cb6f652fef9504360e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/601ed47b2363c24d948d7bac0c23abc8bd459570'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/85e2ce1920cb511d57aae59f0df6ff85b28bf04d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c09ac9a63fc3aaf4670ad7b5e4f5afd764424154'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f2537be4f8421f6495edfa0bc284d722f253841d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00651
epssPercentile: 0.49995
ingestedAt: '2026-10-14T21:57:04.738Z'
---

## Overview

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

nvmet-fc: avoid scheduling association deletion twice

When forcefully shutting down a port via the configfs interface,
nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and
then nvmet_disable_port(). Both functions will eventually schedule all
remaining associations for deletion.

The current implementation checks whether an association is about to be
removed, but only after the work item has already been scheduled. As a
result, it is possible for the first scheduled work item to free all
resources, and then for the same work item to be scheduled again for
deletion.

Because the association list is an RCU list, it is not possible to take
a lock and remove the list entry directly, so it cannot be looked up
again. Instead, a flag (terminating) must be used to determine whether
the association is already in the process of being deleted.

## Remediation

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