Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97537 Overview
CVE-2026-97537 is a Linux kernel vulnerability in the qla2xxx SCSI driver for QLogic Fibre Channel adapters. The flaw affects queue teardown logic in qla25xx_free_req_que() and qla25xx_free_rsp_que(). Two pre-existing bugs surface on the error path of qla25xx_create_{req,rsp}_que(). The first allows dma_free_coherent() to be called with a NULL pointer when dma_alloc_coherent() fails during queue creation. The second involves inconsistent locking: free paths use vport_lock while create paths use mq_lock to protect the same req_qid_map and rsp_qid_map bitmaps. The resolved patch guards the DMA free with a NULL check and consolidates bitmap operations under mq_lock.
Critical Impact
Local kernel crash or memory corruption through a race window where a reused que_id can have its ha->req_q_map entry clobbered by a lockless NULL assignment.
Affected Products
- Linux kernel versions containing the pre-patch qla2xxx SCSI driver
- Systems using QLogic Fibre Channel host bus adapters with multi-queue support
- Distributions tracking mainline before commits 34a40e0, 94fc0c5, and f35cb67
Discovery Timeline
- 2026-09-25 - CVE-2026-97537 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-97537
Vulnerability Analysis
The vulnerability resides in the qla2xxx driver's queue lifecycle management. When qla25xx_create_req_que() or qla25xx_create_rsp_que() fails after allocating the queue structure with kzalloc but before dma_alloc_coherent() succeeds, the error path invokes the corresponding free function. That free function unconditionally calls dma_free_coherent() on req->ring or rsp->ring, which is still NULL. Passing a NULL cpu_addr to dma_free_coherent() is undefined behavior and can trigger a kernel panic.
The second defect involves lock mismatch. Create paths acquire mq_lock to allocate a que_id from req_qid_map and rsp_qid_map. Free paths acquire vport_lock to clear the same bits. The two locks provide no mutual exclusion against each other. The create error path additionally clears the bit and releases mq_lock before invoking the free function. This opens a window where a parallel thread can allocate the same que_id and populate ha->req_q_map[que_id], only to have the entry overwritten with NULL by the lockless assignment in the free function.
Root Cause
The root cause combines a [Null Pointer Dereference] on the DMA free path with a [Race Condition] produced by inconsistent lock selection across paired allocation and deallocation routines.
Attack Vector
Triggering requires local kernel-level code execution paths that drive queue creation failures on affected QLogic hardware. The vulnerability is not remotely exploitable through network traffic. Exploitation yields denial of service via panic, with the race window permitting memory corruption of the queue map. See the upstream fix commits for the exact code changes: Kernel Git Commit 34a40e0, Kernel Git Commit 94fc0c5, and Kernel Git Commit f35cb67.
Detection Methods for CVE-2026-97537
Indicators of Compromise
- Kernel panic traces referencing dma_free_coherent called from qla25xx_free_req_que or qla25xx_free_rsp_que
- Unexpected NULL entries in ha->req_q_map or ha->rsp_q_map after queue creation failures
- qla2xxx driver log messages reporting DMA allocation failures followed by subsequent queue operation errors
Detection Strategies
- Audit running kernel versions on hosts with QLogic Fibre Channel adapters and compare against patched stable branches
- Review kernel crash dumps for stack frames involving qla25xx_create_req_que, qla25xx_create_rsp_que, or the matching free functions
- Monitor SCSI subsystem error counters for correlated queue teardown failures
Monitoring Recommendations
- Centralize dmesg and kernel ring buffer collection from storage-attached hosts for pattern matching
- Alert on repeated qla2xxx queue creation failures preceding host reboots
- Track package versions of installed kernels to confirm patch adoption across the fleet
How to Mitigate CVE-2026-97537
Immediate Actions Required
- Apply the upstream Linux kernel patches referenced by commits 34a40e0, 94fc0c5, and f35cb67
- Update to a distribution kernel that includes the qla2xxx queue teardown fix
- Prioritize patching on hosts using QLogic Fibre Channel HBAs with multi-queue configurations
Patch Information
The fix guards dma_free_coherent() with a NULL check on the ring pointer, moves bitmap clearing under mq_lock so the map entry and bitmap bit are updated atomically, and removes the now-redundant clear_bit calls from the create error paths. Patches are available via Kernel Git Commit 34a40e0, Kernel Git Commit 94fc0c5, and Kernel Git Commit f35cb67.
Workarounds
- Avoid dynamically creating and destroying qla2xxx request and response queues on unpatched systems
- Limit multi-queue configuration changes to maintenance windows where a potential panic is acceptable
- Restrict local administrative access that can trigger queue reconfiguration until the patch is deployed
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

