CVE-2026-97532

scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path

N/A
Published: September 25, 2026 at 10:21 AM UTC
Updated: October 21, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.274.15.104.167142b10b87d5b393a0688358b16a4b1d3680ec7d8540351ee8a4d540b1b7ee64b88d5e42c7c0bfbcd64d6c5671db5e693a0caaee79f2571b098749c9
Vendor states this is fixed in 286d9594a022dd7e0caa3de9daa63b896bc70d43 (fixed)
Vendor states this is fixed in 6d90f0feb929f6c0f3010f9af4747c7230b75993 (fixed)
Vendor states this is fixed in 84f5de696b8c924aeb4bf430a0bdc762fc50e99f (fixed)
Vendor states this is fixed in a57570229edb7a0990d5c8067daeb9ac8858a961 (fixed)
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.16 (unaffected)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card