CVE-2026-97537

published 25 Sep 2026 · updated 20 Nov 2026

scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f35cb67f2092b49d7949065dd56895ed47238f22, Kernel 2e6f60adf609c77e828f64e0cd371920bef91c12, Kernel 34a40e0dff940ac5eba494a69b553ea571e24873 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que(): 1. When dma_alloc_coherent() fails during queue creation, the error path calls the free function with req->ring / rsp->ring still NULL (from kzalloc). The unconditional dma_free_coherent() with a NULL cpu_addr is undefined behavior and can panic. 2. The free functions clear req_qid_map / rsp_qid_map under vport_lock, but the create functions protect the same bitmaps with mq_lock. This provides no mutual exclusion. Additionally, the create error path clears the bit and releases mq_lock before calling the free function, creating a window where another thread can allocate the same que_id and have its ha->req_q_map entry clobbered by the subsequent lockless NULL assignment in the free function. Fix by: - Guarding dma_free_coherent() with a NULL check on the ring pointer. - Using mq_lock (the lock held by all creators) in the free functions to atomically NULL the map entry and clear the bitmap bit. - Removing the now-redundant clear_bit blocks from the create error paths since the free functions handle it atomically.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <f35cb67f2092b49d7949065dd56895ed47238f22, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <2e6f60adf609c77e828f64e0cd371920bef91c12, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <34a40e0dff940ac5eba494a69b553ea571e24873, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <56e25d716833604fd5bff388e472f290bfe793aa, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <81ee4df2a488f0909f7ff563e88a0e0099485a8b, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <94fc0c5b45de2bf3a691619bcfd10b9a49fc647e, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <a9ff85886425355c72749be6090758aa19a89f16, >=73208dfd7ab19f379d73e8a0fbf30f92c203e5e8 <b65e3a82f77b7a63e386623d2ea70d2b5580295a, =2.6.29f35cb67f2092b49d7949065dd56895ed47238f22, 2e6f60adf609c77e828f64e0cd371920bef91c12, 34a40e0dff940ac5eba494a69b553ea571e24873, 56e25d716833604fd5bff388e472f290bfe793aa, 81ee4df2a488f0909f7ff563e88a0e0099485a8b, 94fc0c5b45de2bf3a691619bcfd10b9a49fc647e, a9ff85886425355c72749be6090758aa19a89f16, b65e3a82f77b7a63e386623d2ea70d2b5580295a
linux-kernel: Kernel>=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.160, >=6.7.0 <6.12.112, >=2.6.29 <5.10.2735.15.224, 6.1.191, 6.18.53, 7.2.7, 6.6.160, 6.12.112, 5.10.273

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97537 severity on Zeptric[![CVE-2026-97537](https://zeptric.io/badge/cve/CVE-2026-97537.svg)](https://zeptric.io/cve/CVE-2026-97537)