scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock
CVE-2026-97527 · published 25 Sept 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-97527?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 875386b98857822b77ac7f95bdf367b70af5b78c to < 6c71726cdfda93ae169a75c7b1697eb870303125, 875386b98857822b77ac7f95bdf367b70af5b78c to < c1ee12eecbab9674fb73c9e00a93fac655d5a5dc, 875386b98857822b77ac7f95bdf367b70af5b78c to < b211d138cad86f749826d6132db6388eded992d8, 875386b98857822b77ac7f95bdf367b70af5b78c to < 4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0
- Linux Linux: 6.6
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/6c71726cdfda93ae169a75c7b1697eb870303125
- git.kernel.org/stable/c/c1ee12eecbab9674fb73c9e00a93fac655d5a5dc
- git.kernel.org/stable/c/b211d138cad86f749826d6132db6388eded992d8
- git.kernel.org/stable/c/4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0
- git.kernel.org/stable/c/76da0c43c63eb0496649e372ac64466364d0fe7d
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON