<?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 16:53:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02405</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-02405</link>
      <description>bdu:2026-02405</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-02405</guid>
    </item>
    <item>
      <title>CVE-2023-53322 — scsi: qla2xxx: Wait for io return on terminate rport</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53322</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: Wait for io return on terminate rport&lt;/p&gt;
&lt;p&gt;System crash due to use after free.
Current code allows terminate_rport_io to exit before making
sure all IOs has returned. For FCP-2 device, IO&amp;#39;s can hang
on in HW because driver has not tear down the session in FW at
first sign of cable pull. When dev_loss_tmo timer pops,
terminate_rport_io is called and upper layer is about to
free various resources. Terminate_rport_io trigger qla to do
the final cleanup, but the cleanup might not be fast enough where it
leave qla still holding on to the same resource.&lt;/p&gt;
&lt;p&gt;Wait for IO&amp;#39;s to return to upper layer before resources are freed.&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: Wait for io return on terminate rport&lt;/p&gt;
&lt;p&gt;System crash due to use after free.
Current code allows terminate_rport_io to exit before making
sure all IOs has returned. For FCP-2 device, IO&amp;#39;s can hang
on in HW because driver has not tear down the session in FW at
first sign of cable pull. When dev_loss_tmo timer pops,
terminate_rport_io is called and upper layer is about to
free various resources. Terminate_rport_io trigger qla to do
the final cleanup, but the cleanup might not be fast enough where it
leave qla still holding on to the same resource.&lt;/p&gt;
&lt;p&gt;Wait for IO&amp;#39;s to return to upper layer before resources are freed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53322</guid>
    </item>
  </channel>
</rss>
