scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown
CVE-2026-97536 · published 25 Sept 2026
How serious is it
- Severity: high, CVSS score 7.5 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-97536?
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: 68ca949cdb04b4dc71451a999148fbc5f187a220 to < 9bd063c082ef0475dfc28c46f607aa3e90fe13d7, 68ca949cdb04b4dc71451a999148fbc5f187a220 to < dd6c14db0dbb7774278e62c8114902f953540932, 68ca949cdb04b4dc71451a999148fbc5f187a220 to < 1710a69fd74d0b4bdfcc57c3309b1c4057f70d85, 68ca949cdb04b4dc71451a999148fbc5f187a220 to < f1f4d1cb93eeeb250eac9405121933e268eefbd3
- Linux Linux: 2.6.31
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: Fix use-after-free of qpair work on queue teardown
The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules
qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work()
dereferences the qpair (vha, rsp) and takes qpair->qp_lock.
During teardown, qla2xxx_delete_qpair() deletes the response queue, which
calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and
the qpair. free_irq() waits for running hardirq handlers but does not
cancel work already placed on ha->wq. A still-pending q_work then runs
qla_do_work() against the freed qpair and response queue, causing a
use-after-free. This is especially likely during full adapter teardown,
where destroy_workqueue(ha->wq) forces pending work to run after the queue
pairs have been freed.
Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que()
after free_irq() has released the interrupt (so no new work can be
queued) and before the response queue and qpair memory are freed (so the
flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq
to match the INIT_WORK() condition and avoid operating on an
uninitialized work_struct.
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/9bd063c082ef0475dfc28c46f607aa3e90fe13d7
- git.kernel.org/stable/c/dd6c14db0dbb7774278e62c8114902f953540932
- git.kernel.org/stable/c/1710a69fd74d0b4bdfcc57c3309b1c4057f70d85
- git.kernel.org/stable/c/f1f4d1cb93eeeb250eac9405121933e268eefbd3
- git.kernel.org/stable/c/19788a55cab61d78e33e0914a5a31d27843e8a4a
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON