CVE-2026-97537: Linux Vulnerability

Description

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.

Metrics

EPSS Probability

0.21%

10.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < b65e3a82f77b7a63e386623d2ea70d2b5580295a; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < a9ff85886425355c72749be6090758aa19a89f16; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < 81ee4df2a488f0909f7ff563e88a0e0099485a8b; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < 2e6f60adf609c77e828f64e0cd371920bef91c12; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < 56e25d716833604fd5bff388e472f290bfe793aa; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < f35cb67f2092b49d7949065dd56895ed47238f22; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < 94fc0c5b45de2bf3a691619bcfd10b9a49fc647e; >= 73208dfd7ab19f379d73e8a0fbf30f92c203e5e8, < 34a40e0dff940ac5eba494a69b553ea571e24873
Linux	Linux	2.6.29

References

Timeline

Published: Sep 25, 2026
Last Modified: Oct 30, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-97537?

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.

How severe is CVE-2026-97537?

Severity scoring for CVE-2026-97537 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.

How do I fix CVE-2026-97537?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →