<?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 22:06:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38620 — zloop: fix KASAN use-after-free of tag set</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38620</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;zloop: fix KASAN use-after-free of tag set&lt;/p&gt;
&lt;p&gt;When a zoned loop device, or zloop device, is removed, KASAN enabled
kernel reports &amp;#34;BUG KASAN use-after-free&amp;#34; in blk_mq_free_tag_set(). The
BUG happens because zloop_ctl_remove() calls put_disk(), which invokes
zloop_free_disk(). The zloop_free_disk() frees the memory allocated for
the zlo pointer. However, after the memory is freed, zloop_ctl_remove()
calls blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set), which accesses the freed zlo.
Hence the KASAN use-after-free.&lt;/p&gt;
&lt;p&gt;zloop_ctl_remove()
  put_disk(zlo-&amp;gt;disk)
   put_device()
    kobject_put()
     ...
      zloop_free_disk()
        kvfree(zlo)
  blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set)&lt;/p&gt;
&lt;p&gt;To avoid the BUG, move the call to blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set)
from zloop_ctl_remove() into zloop_free_disk(). This ensures that
the tag_set is freed before the call to kvfree(zlo).&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;zloop: fix KASAN use-after-free of tag set&lt;/p&gt;
&lt;p&gt;When a zoned loop device, or zloop device, is removed, KASAN enabled
kernel reports &amp;#34;BUG KASAN use-after-free&amp;#34; in blk_mq_free_tag_set(). The
BUG happens because zloop_ctl_remove() calls put_disk(), which invokes
zloop_free_disk(). The zloop_free_disk() frees the memory allocated for
the zlo pointer. However, after the memory is freed, zloop_ctl_remove()
calls blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set), which accesses the freed zlo.
Hence the KASAN use-after-free.&lt;/p&gt;
&lt;p&gt;zloop_ctl_remove()
  put_disk(zlo-&amp;gt;disk)
   put_device()
    kobject_put()
     ...
      zloop_free_disk()
        kvfree(zlo)
  blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set)&lt;/p&gt;
&lt;p&gt;To avoid the BUG, move the call to blk_mq_free_tag_set(&amp;amp;zlo-&amp;gt;tag_set)
from zloop_ctl_remove() into zloop_free_disk(). This ensures that
the tag_set is freed before the call to kvfree(zlo).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38620</guid>
    </item>
  </channel>
</rss>
