<?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>Wed, 30 Sep 2026 23:23:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23261 — nvme-fc: release admin tagset if init fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23261</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;nvme-fc: release admin tagset if init fails&lt;/p&gt;
&lt;p&gt;nvme_fabrics creates an NVMe/FC controller in following path:&lt;/p&gt;
&lt;p&gt;nvmf_dev_write()
      -&amp;gt; nvmf_create_ctrl()
        -&amp;gt; nvme_fc_create_ctrl()
          -&amp;gt; nvme_fc_init_ctrl()&lt;/p&gt;
&lt;p&gt;nvme_fc_init_ctrl() allocates the admin blk-mq resources right after
nvme_add_ctrl() succeeds.  If any of the subsequent steps fail (changing
the controller state, scheduling connect work, etc.), we jump to the
fail_ctrl path, which tears down the controller references but never
frees the admin queue/tag set.  The leaked blk-mq allocations match the
kmemleak report seen during blktests nvme/fc.&lt;/p&gt;
&lt;p&gt;Check ctrl-&amp;gt;ctrl.admin_tagset in the fail_ctrl path and call
nvme_remove_admin_tag_set() when it is set so that all admin queue
allocations are reclaimed whenever controller setup aborts.&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;nvme-fc: release admin tagset if init fails&lt;/p&gt;
&lt;p&gt;nvme_fabrics creates an NVMe/FC controller in following path:&lt;/p&gt;
&lt;p&gt;nvmf_dev_write()
      -&amp;gt; nvmf_create_ctrl()
        -&amp;gt; nvme_fc_create_ctrl()
          -&amp;gt; nvme_fc_init_ctrl()&lt;/p&gt;
&lt;p&gt;nvme_fc_init_ctrl() allocates the admin blk-mq resources right after
nvme_add_ctrl() succeeds.  If any of the subsequent steps fail (changing
the controller state, scheduling connect work, etc.), we jump to the
fail_ctrl path, which tears down the controller references but never
frees the admin queue/tag set.  The leaked blk-mq allocations match the
kmemleak report seen during blktests nvme/fc.&lt;/p&gt;
&lt;p&gt;Check ctrl-&amp;gt;ctrl.admin_tagset in the fail_ctrl path and call
nvme_remove_admin_tag_set() when it is set so that all admin queue
allocations are reclaimed whenever controller setup aborts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23261</guid>
    </item>
  </channel>
</rss>
