CVE-2026-97409

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

  • High 8.8

Description

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.

Key facts

Published
24 Sep 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.254% likely to be exploited in the next 30 days, higher than 17.033% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 52793d62a696e9188092eb0817fb1219ee5729ff up to but excluding 0b7c8009b3037722103032c336732d63e0507a51 (affected)
  • 52793d62a696e9188092eb0817fb1219ee5729ff up to but excluding 5488e2706c58444a24e15773237dcc0bedcd771f (affected)
  • 52793d62a696e9188092eb0817fb1219ee5729ff up to but excluding da930308b4bc24c335574e85ca84ff70a988cf05 (affected)
  • 52793d62a696e9188092eb0817fb1219ee5729ff up to but excluding dd39064d2948b14dbe4f364fe4b3c9cfc632cc21 (affected)
  • 52793d62a696e9188092eb0817fb1219ee5729ff up to but excluding ee38469f88492df99e1d97f03aa40ecfd218934f (affected)
LinuxLinux
  • Default status: affected
  • 5.10 (affected)
  • 0 up to but excluding 5.10 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References