Answer in brief
CVE-2026-97532 records a Unknown severity vulnerability in scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a57570229edb7a0990d5c8067daeb9ac8858a961 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <286d9594a022dd7e0caa3de9daa63b896bc70d43 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d90f0feb929f6c0f3010f9af4747c7230b75993 || >=0 <6.18.53 || >=0 <7.2.7 | a57570229edb7a0990d5c8067daeb9ac8858a961, 286d9594a022dd7e0caa3de9daa63b896bc70d43, 6d90f0feb929f6c0f3010f9af4747c7230b75993, 6.18.53, 7.2.7 |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.