HIGH Introduced in 6.6
qla2xxx UnsolCtx Race
CVE-2026-97527
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.5HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock The fcport->unsol_ctx_head list is modified from several contexts without a common lock. Entries are added in qla2xxx_process_purls_iocb() from the response queue ISR (under the qpair qp_lock), while they are removed from qla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp() (NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB completion). The qpair qp_lock cannot serialize this per-fcport list since multiqueue adapters add entries through different qpairs, so a concurrent add and delete (or two concurrent deletes) can corrupt the list pointers. Introduce a dedicated per-fcport spinlock, unsol_ctx_lock, initialized in qla2x00_alloc_fcport(), and take it around every list_add_tail()/list_del() on unsol_ctx_head. The add nests under the existing qp_lock; no delete path takes qp_lock, so the lock order is consistent and deadlock free.
02KernelScan AI Analysis
Risk summary
An attacker on the same Fibre Channel fabric can send unsolicited NVMe LS requests that trigger concurrent list add and delete operations on a per-fcport context list, corrupting linked-list pointers. This can lead to kernel memory corruption, information disclosure, or a system crash. The vulnerability requires a QLogic Fibre Channel adapter and connectivity to an FC fabric where an attacker can inject frames.
Vulnerability analysis
A linked list that tracks unsolicited NVMe link-service contexts for each port is modified from several execution contexts—including an interrupt handler, a worker thread, a transport callback, and command completion—without any common lock. On adapters with multiple queues, entries can be added through different queues at the same time deletions happen on other paths, corrupting the list pointers and leading to memory corruption. The fix adds a dedicated spinlock for each port that serializes every list insertion and removal, nesting consistently under the existing queue lock on the add path and taken independently on all removal paths. The vulnerable code is reached when the host receives unsolicited NVMe link-service requests over the Fibre Channel fabric, so an attacker needs access to the same fabric and a vulnerable adapter must be present, but no privileges on the target system are required.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.12 | 6.6 | 6.12.112 | c1ee12eecbab |
| 6.18 | 6.6 | 6.18.53 | b211d138cad8 |
| 6.6 | 6.6 | 6.6.160 | 6c71726cdfda |
| 7.2 | 6.6 | 7.2.7 | 4d8ad6bc8cc5 |
| mainline | 6.6 | 7.3 | 76da0c43c63e |
| cip/6.12 | 6.6 | 6.12.112-cip33 | c1ee12eecbab |
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.112-cip33 |