<?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 13:03:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89847 — scsi: qla2xxx: Avoid double completion in async IOCB timeout</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89847</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: Avoid double completion in async IOCB timeout&lt;/p&gt;
&lt;p&gt;qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When
qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the
SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then
call sp-&amp;gt;done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking
whether the SRB was actually found and removed.&lt;/p&gt;
&lt;p&gt;If the response ISR completes the same handle first, it removes the SRB
under qp_lock_ptr and runs sp-&amp;gt;done() -&amp;gt; complete(sp-&amp;gt;comp). The
submitter qla24xx_control_vp() wakes from wait_for_completion(), clears
sp-&amp;gt;comp, drops its reference and returns, reclaiming the on-stack
completion. The timer reference keeps the SRB alive across the timeout
handler, but not the submitter&amp;#39;s stack. The timeout then issues a second
sp-&amp;gt;done() -&amp;gt; qla_ctrlvp_sp_done(), which evaluates &amp;#34;if (sp-&amp;gt;comp)
complete(sp-&amp;gt;comp)&amp;#34;; with the pointer loaded before the submitter&amp;#39;s NULL
store, complete() writes into the freed stack frame, a use-after-free.&lt;/p&gt;
&lt;p&gt;Track whether this path removed the SRB from outstanding_cmds and only
call sp-&amp;gt;done() when it did, so the command is completed exactly once by
whichever path owns it. This mirrors the sp_found guard already used in
qla24xx_abort_iocb_timeout().&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: Avoid double completion in async IOCB timeout&lt;/p&gt;
&lt;p&gt;qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When
qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the
SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then
call sp-&amp;gt;done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking
whether the SRB was actually found and removed.&lt;/p&gt;
&lt;p&gt;If the response ISR completes the same handle first, it removes the SRB
under qp_lock_ptr and runs sp-&amp;gt;done() -&amp;gt; complete(sp-&amp;gt;comp). The
submitter qla24xx_control_vp() wakes from wait_for_completion(), clears
sp-&amp;gt;comp, drops its reference and returns, reclaiming the on-stack
completion. The timer reference keeps the SRB alive across the timeout
handler, but not the submitter&amp;#39;s stack. The timeout then issues a second
sp-&amp;gt;done() -&amp;gt; qla_ctrlvp_sp_done(), which evaluates &amp;#34;if (sp-&amp;gt;comp)
complete(sp-&amp;gt;comp)&amp;#34;; with the pointer loaded before the submitter&amp;#39;s NULL
store, complete() writes into the freed stack frame, a use-after-free.&lt;/p&gt;
&lt;p&gt;Track whether this path removed the SRB from outstanding_cmds and only
call sp-&amp;gt;done() when it did, so the command is completed exactly once by
whichever path owns it. This mirrors the sp_found guard already used in
qla24xx_abort_iocb_timeout().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89847</guid>
    </item>
  </channel>
</rss>
