{"id":"AZL-104723","summary":"CVE-2026-97537 affecting package kernel 6.6.157.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking\n\nqla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing\nbugs exposed on the error path of qla25xx_create_{req,rsp}_que():\n\n 1. When dma_alloc_coherent() fails during queue creation, the error\n    path calls the free function with req-\u003ering / rsp-\u003ering still NULL\n    (from kzalloc).  The unconditional dma_free_coherent() with a NULL\n    cpu_addr is undefined behavior and can panic.\n\n 2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,\n    but the create functions protect the same bitmaps with mq_lock.\n    This provides no mutual exclusion.  Additionally, the create error\n    path clears the bit and releases mq_lock before calling the free\n    function, creating a window where another thread can allocate the\n    same que_id and have its ha-\u003ereq_q_map entry clobbered by the\n    subsequent lockless NULL assignment in the free function.\n\nFix by:\n\n - Guarding dma_free_coherent() with a NULL check on the ring pointer.\n\n - Using mq_lock (the lock held by all creators) in the free functions\n   to atomically NULL the map entry and clear the bitmap bit.\n\n - Removing the now-redundant clear_bit blocks from the create error\n   paths since the free functions handle it atomically.","modified":"2026-09-27T05:34:32Z","published":"2026-09-25T11:17:03Z","upstream":["CVE-2026-97537"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97537"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.157.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-104723.json"}}],"schema_version":"1.9.0"}