<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 05:34:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97537 — scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97537</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking&lt;/p&gt;
&lt;p&gt;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():&lt;/p&gt;
&lt;p&gt;1. When dma_alloc_coherent() fails during queue creation, the error
    path calls the free function with req-&amp;gt;ring / rsp-&amp;gt;ring still NULL
    (from kzalloc).  The unconditional dma_free_coherent() with a NULL
    cpu_addr is undefined behavior and can panic.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;req_q_map entry clobbered by the
    subsequent lockless NULL assignment in the free function.&lt;/p&gt;
&lt;p&gt;Fix by:&lt;/p&gt;
&lt;p&gt;- Guarding dma_free_coherent() with a NULL check on the ring pointer.&lt;/p&gt;
&lt;p&gt;- Using mq_lock (the lock held by all creators) in the free functions
   to atomically NULL the map entry and clear the bitmap bit.&lt;/p&gt;
&lt;p&gt;- Removing the now-redundant clear_bit blocks from the create error
   paths since the free functions handle it atomically.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking&lt;/p&gt;
&lt;p&gt;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():&lt;/p&gt;
&lt;p&gt;1. When dma_alloc_coherent() fails during queue creation, the error
    path calls the free function with req-&amp;gt;ring / rsp-&amp;gt;ring still NULL
    (from kzalloc).  The unconditional dma_free_coherent() with a NULL
    cpu_addr is undefined behavior and can panic.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;req_q_map entry clobbered by the
    subsequent lockless NULL assignment in the free function.&lt;/p&gt;
&lt;p&gt;Fix by:&lt;/p&gt;
&lt;p&gt;- Guarding dma_free_coherent() with a NULL check on the ring pointer.&lt;/p&gt;
&lt;p&gt;- Using mq_lock (the lock held by all creators) in the free functions
   to atomically NULL the map entry and clear the bitmap bit.&lt;/p&gt;
&lt;p&gt;- Removing the now-redundant clear_bit blocks from the create error
   paths since the free functions handle it atomically.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97537</guid>
    </item>
  </channel>
</rss>
