HIGH Introduced in 5.10
nvme-fc TagSet Race
CVE-2026-97409
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
KernelScan AI4.1MEDIUM
01Description
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.
02KernelScan AI Analysis
Risk summary
A race condition in the NVMe-over-Fibre Channel driver allows error recovery work to access an I/O tagset before it has been initialized, leading to a kernel crash or lockdep validator shutdown. The bug is triggered when a newly created NVMe-FC controller in CONNECTING state experiences an admin request timeout. Exploitation requires local privileged access (root or equivalent) to initiate NVMe-FC controller creation, plus FC hardware and an unreachable or failing FC target.
Vulnerability analysis
When a new NVMe-FC controller is connecting and its admin request times out, the driver schedules error recovery work that attempts to abort outstanding requests across both the admin and I/O paths. The driver marks that I/O queues will exist before the structures that track those requests are actually initialized. If the error recovery work fires in this window, it iterates over uninitialized tracking state, causing the block layer to use uninitialized lock structures and potentially crash the kernel. The fix adds a check so the I/O tracking state is only used when it has actually been created, and ensures the error recovery work is cancelled before that state is removed during cleanup. This path is reachable only by a privileged local user who can create NVMe-FC controllers on a system with Fibre Channel hardware, and the trigger is a connection failure or timeout to an FC target.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.12 | 5.10 | 6.12.111 | da930308b4bc |
| 6.18 | 5.10 | 6.18.53 | dd39064d2948 |
| 6.6 | 5.10 | 6.6.158 | 5488e2706c58 |
| mainline | 5.10 | 7.2 | ee38469f8849 |
| cip/6.12 | 5.10 | 6.12.111-cip32 | da930308b4bc |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.111-cip32 |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.189-cip61) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.271-cip78) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.268-cip77-rt34) |