<?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 06:26:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89848 — scsi: qla2xxx: Quiesce response IRQ before freeing request queue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89848</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: Quiesce response IRQ before freeing request queue&lt;/p&gt;
&lt;p&gt;qla2xxx_delete_qpair() deletes the request queue before the response
queue. qla25xx_delete_req_que() frees the request queue memory
(kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is
only released later, in qla25xx_free_rsp_que(). In that window the
response interrupt can still fire, qla2xxx_msix_rsp_q() queues
qpair-&amp;gt;q_work, and qla_do_work() -&amp;gt; qla24xx_process_response_queue()
dereferences the now-freed rsp-&amp;gt;req (LOGINOUT/CT/ELS entries and the
status path), a use-after-free.&lt;/p&gt;
&lt;p&gt;The cancel_work_sync() added for the qpair teardown lives in the
response free path, which runs after the request queue is already freed,
so it does not protect rsp-&amp;gt;req.&lt;/p&gt;
&lt;p&gt;Release the response-queue interrupt and flush qpair-&amp;gt;q_work before
deleting the request queue, so no late completion can reach the freed
request queue. Clearing have_irq makes the subsequent
qla25xx_free_rsp_que() skip its free_irq(), and the firmware
queue-delete order (request then response) is preserved; the
request-delete mailbox completes on the default vector and is unaffected
by dropping the qpair response interrupt early.&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: Quiesce response IRQ before freeing request queue&lt;/p&gt;
&lt;p&gt;qla2xxx_delete_qpair() deletes the request queue before the response
queue. qla25xx_delete_req_que() frees the request queue memory
(kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is
only released later, in qla25xx_free_rsp_que(). In that window the
response interrupt can still fire, qla2xxx_msix_rsp_q() queues
qpair-&amp;gt;q_work, and qla_do_work() -&amp;gt; qla24xx_process_response_queue()
dereferences the now-freed rsp-&amp;gt;req (LOGINOUT/CT/ELS entries and the
status path), a use-after-free.&lt;/p&gt;
&lt;p&gt;The cancel_work_sync() added for the qpair teardown lives in the
response free path, which runs after the request queue is already freed,
so it does not protect rsp-&amp;gt;req.&lt;/p&gt;
&lt;p&gt;Release the response-queue interrupt and flush qpair-&amp;gt;q_work before
deleting the request queue, so no late completion can reach the freed
request queue. Clearing have_irq makes the subsequent
qla25xx_free_rsp_que() skip its free_irq(), and the firmware
queue-delete order (request then response) is preserved; the
request-delete mailbox completes on the default vector and is unaffected
by dropping the qpair response interrupt early.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89848</guid>
    </item>
  </channel>
</rss>
