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

  nvme-fc: Do not cancel requests in io target before it is initialized

  A new nvme-fc controller in CONNECTING state sees admin request timeout
  schedules ctrl->ioerr_wor…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvme-fc: Do not cancel requests in io target before it is initialized

  A new nvme-fc controller in CONNECTING state sees admin request timeout
  schedules ctrl->ioerr_wor…
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'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 52793d62a696e9188092eb0817fb1219ee5729ff <
    5488e2706c58444a24e15773237dcc0bedcd771f
  - >-
    Linux >= 52793d62a696e9188092eb0817fb1219ee5729ff <
    da930308b4bc24c335574e85ca84ff70a988cf05
  - >-
    Linux >= 52793d62a696e9188092eb0817fb1219ee5729ff <
    dd39064d2948b14dbe4f364fe4b3c9cfc632cc21
  - >-
    Linux >= 52793d62a696e9188092eb0817fb1219ee5729ff <
    ee38469f88492df99e1d97f03aa40ecfd218934f
  - Linux 5.10
published: '2026-09-24'
updated: '2026-10-03'
sourceUpdated: '2026-10-03T11:17:53.063'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97409'
references:
  - url: 'https://git.kernel.org/stable/c/5488e2706c58444a24e15773237dcc0bedcd771f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/da930308b4bc24c335574e85ca84ff70a988cf05'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/dd39064d2948b14dbe4f364fe4b3c9cfc632cc21'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ee38469f88492df99e1d97f03aa40ecfd218934f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97409.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-97409'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2540444'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-97409'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97409'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-97409.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
  - score-dispute
epss: 0.00241
epssPercentile: 0.15218
ingestedAt: '2026-09-24T16:47:15.888Z'
cwe:
  - CWE-908
scores:
  nvd: 8.8
  vendor: 5.5
---

## Overview

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

nvme-fc: Do not cancel requests in io target before it is initialized

A new nvme-fc controller in CONNECTING state sees admin request timeout
schedules ctrl->ioerr_work to abort inflight requests. This ends up
calling __nvme_fc_abort_outstanding_ios() which aborts requests in both
admin and io tagsets. In case fc_ctrl->tag_set was not initialized we
see the warning below. This is because ctrl.queue_count is initialized
early in nvme_fc_alloc_ctrl().

nvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
lpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6).
you didn't initialize this object before use?
turning off the locking correctness validator.
Workqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc]
Call Trace:
 <TASK>
 dump_stack_lvl+0x57/0x80
 register_lock_class+0x567/0x580
 __lock_acquire+0x330/0xb90
 lock_acquire.part.0+0xad/0x210
 blk_mq_tagset_busy_iter+0xf9/0xc00
 __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc]
 nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc]
 process_one_work+0x82c/0x1450
 worker_thread+0x5ee/0xfd0
 kthread+0x3a0/0x750
 ret_from_fork+0x439/0x670
 ret_from_fork_asm+0x1a/0x30
 </TASK>

Update the check in __nvme_fc_abort_outstanding_ios() confirm that io
tagset was created before iterating over busy requests. Also make sure
to cancel ctrl->ioerr_work before removing io tagset.

## Remediation

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

## Vendor advisories

- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · updated 2026-10-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97409.json)