<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 16:09:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02821</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02821</link>
      <description>bdu:2026-02821</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02821</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38620</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38620</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38620</guid>
    </item>
    <item>
      <title>EUVD-2026-314681</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314681</link>
      <description>EUVD-2026-314681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314681</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38620</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38620</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2025-38620</guid>
    </item>
    <item>
      <title>GHSA-hjhr-hvpq-97f6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hjhr-hvpq-97f6</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-hjhr-hvpq-97f6</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38620</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38620</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: zloop: fix KASAN use-after-free of tag set 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.  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) 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: zloop: fix KASAN use-after-free of tag set 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.  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) 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://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38620</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und Privilegieneskalation</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</guid>
    </item>
  </channel>
</rss>
