<?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>Mon, 28 Sep 2026 06:37:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89853 — scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89853</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 FCE trace use-after-free during firmware dump&lt;/p&gt;
&lt;p&gt;qla2x00_free_fce_trace() freed and cleared ha-&amp;gt;fce while holding only
fce_mutex. The firmware-dump consumers qla27xx_fwdt_entry_t264() and
qla25xx_copy_fce() read ha-&amp;gt;fce (NULL check followed by a copy of the
buffer) under hardware_lock and never take fce_mutex. A debugfs FCE
disable could therefore free the DMA buffer between a dump&amp;#39;s NULL check
and its copy, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Unpublish ha-&amp;gt;fce under hardware_lock, then release the lock and free
the DMA buffer (dma_free_coherent() may sleep). A concurrent dump either
completes its check and copy with the buffer still valid, or observes
ha-&amp;gt;fce == NULL and skips it.&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 FCE trace use-after-free during firmware dump&lt;/p&gt;
&lt;p&gt;qla2x00_free_fce_trace() freed and cleared ha-&amp;gt;fce while holding only
fce_mutex. The firmware-dump consumers qla27xx_fwdt_entry_t264() and
qla25xx_copy_fce() read ha-&amp;gt;fce (NULL check followed by a copy of the
buffer) under hardware_lock and never take fce_mutex. A debugfs FCE
disable could therefore free the DMA buffer between a dump&amp;#39;s NULL check
and its copy, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Unpublish ha-&amp;gt;fce under hardware_lock, then release the lock and free
the DMA buffer (dma_free_coherent() may sleep). A concurrent dump either
completes its check and copy with the buffer still valid, or observes
ha-&amp;gt;fce == NULL and skips it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89853</guid>
    </item>
  </channel>
</rss>
