<?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 20:23:02 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74513</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74513</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74513</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1255 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1255</link>
      <description>certfr-2026-avi-1255</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1255</guid>
    </item>
    <item>
      <title>EUVD-2026-354241</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354241</link>
      <description>EUVD-2026-354241</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354241</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74513</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74513</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister&lt;/p&gt;
&lt;p&gt;dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb()
look up the dmb_node under dmb_ht_lock, drop the lock and only then
operate on the node&amp;#39;s refcount. Nothing keeps the node alive across
that window: __dibs_lo_unregister_dmb() removes the node from the hash
table under the write lock and immediately frees it.&lt;/p&gt;
&lt;p&gt;A concurrent final put can therefore free the node between the lookup
and the refcount operation:&lt;/p&gt;
&lt;p&gt;CPU0 (attach)                     CPU1 (owner unregisters)&lt;/p&gt;
&lt;p&gt;read_lock_bh(&amp;amp;dmb_ht_lock)
find dmb_node (refcnt == 1)
read_unlock_bh(&amp;amp;dmb_ht_lock)
                                  refcount_dec_and_test() 1 -&amp;gt; 0
                                  write_lock_bh(&amp;amp;dmb_ht_lock)
                                  hash_del(&amp;amp;dmb_node-&amp;gt;list)
                                  write_unlock_bh(&amp;amp;dmb_ht_lock)
                                  kfree(dmb_node)
refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;The same window exists for the refcount_dec_and_test() calls in the
detach and unregister paths.&lt;/p&gt;
&lt;p&gt;Close the race structurally by making hash table membership and the
refcount transitions atomic with respect to each other:&lt;/p&gt;
&lt;p&gt;- Perform the final refcount_dec_and_test() and hash_del() in a single
  dmb_ht_lock write-side critical section, in both the unregister and
  the detach path. Freeing the node still happens af…&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;dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister&lt;/p&gt;
&lt;p&gt;dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb()
look up the dmb_node under dmb_ht_lock, drop the lock and only then
operate on the node&amp;#39;s refcount. Nothing keeps the node alive across
that window: __dibs_lo_unregister_dmb() removes the node from the hash
table under the write lock and immediately frees it.&lt;/p&gt;
&lt;p&gt;A concurrent final put can therefore free the node between the lookup
and the refcount operation:&lt;/p&gt;
&lt;p&gt;CPU0 (attach)                     CPU1 (owner unregisters)&lt;/p&gt;
&lt;p&gt;read_lock_bh(&amp;amp;dmb_ht_lock)
find dmb_node (refcnt == 1)
read_unlock_bh(&amp;amp;dmb_ht_lock)
                                  refcount_dec_and_test() 1 -&amp;gt; 0
                                  write_lock_bh(&amp;amp;dmb_ht_lock)
                                  hash_del(&amp;amp;dmb_node-&amp;gt;list)
                                  write_unlock_bh(&amp;amp;dmb_ht_lock)
                                  kfree(dmb_node)
refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;The same window exists for the refcount_dec_and_test() calls in the
detach and unregister paths.&lt;/p&gt;
&lt;p&gt;Close the race structurally by making hash table membership and the
refcount transitions atomic with respect to each other:&lt;/p&gt;
&lt;p&gt;- Perform the final refcount_dec_and_test() and hash_del() in a single
  dmb_ht_lock write-side critical section, in both the unregister and
  the detach path. Freeing the node still happens af…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74513</guid>
    </item>
    <item>
      <title>GHSA-p4c6-79fv-gqjg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p4c6-79fv-gqjg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister&lt;/p&gt;
&lt;p&gt;dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb()
look up the dmb_node under dmb_ht_lock, drop the lock and only then
operate on the node&amp;#39;s refcount. Nothing keeps the node alive across
that window: __dibs_lo_unregister_dmb() removes the node from the hash
table under the write lock and immediately frees it.&lt;/p&gt;
&lt;p&gt;A concurrent final put can therefore free the node between the lookup
and the refcount operation:&lt;/p&gt;
&lt;p&gt;CPU0 (attach)                     CPU1 (owner unregisters)&lt;/p&gt;
&lt;p&gt;read_lock_bh(&amp;amp;dmb_ht_lock)
find dmb_node (refcnt == 1)
read_unlock_bh(&amp;amp;dmb_ht_lock)
                                  refcount_dec_and_test() 1 -&amp;gt; 0
                                  write_lock_bh(&amp;amp;dmb_ht_lock)
                                  hash_del(&amp;amp;dmb_node-&amp;gt;list)
                                  write_unlock_bh(&amp;amp;dmb_ht_lock)
                                  kfree(dmb_node)
refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;The same window exists for the refcount_dec_and_test() calls in the
detach and unregister paths.&lt;/p&gt;
&lt;p&gt;Close the race structurally by making hash table membership and the
refcount transitions atomic with respect to each other:&lt;/p&gt;
&lt;p&gt;- Perform the final refcount_dec_and_test() and hash_del() in a single
  dmb_ht_lock write-side critical section, in both the unregister and
  the detach path. Freeing the node still happens af…&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;dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister&lt;/p&gt;
&lt;p&gt;dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb()
look up the dmb_node under dmb_ht_lock, drop the lock and only then
operate on the node&amp;#39;s refcount. Nothing keeps the node alive across
that window: __dibs_lo_unregister_dmb() removes the node from the hash
table under the write lock and immediately frees it.&lt;/p&gt;
&lt;p&gt;A concurrent final put can therefore free the node between the lookup
and the refcount operation:&lt;/p&gt;
&lt;p&gt;CPU0 (attach)                     CPU1 (owner unregisters)&lt;/p&gt;
&lt;p&gt;read_lock_bh(&amp;amp;dmb_ht_lock)
find dmb_node (refcnt == 1)
read_unlock_bh(&amp;amp;dmb_ht_lock)
                                  refcount_dec_and_test() 1 -&amp;gt; 0
                                  write_lock_bh(&amp;amp;dmb_ht_lock)
                                  hash_del(&amp;amp;dmb_node-&amp;gt;list)
                                  write_unlock_bh(&amp;amp;dmb_ht_lock)
                                  kfree(dmb_node)
refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;The same window exists for the refcount_dec_and_test() calls in the
detach and unregister paths.&lt;/p&gt;
&lt;p&gt;Close the race structurally by making hash table membership and the
refcount transitions atomic with respect to each other:&lt;/p&gt;
&lt;p&gt;- Perform the final refcount_dec_and_test() and hash_del() in a single
  dmb_ht_lock write-side critical section, in both the unregister and
  the detach path. Freeing the node still happens af…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p4c6-79fv-gqjg</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74513</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74513</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb() look up the dmb_node under dmb_ht_lock, drop the lock and only then operate on the node&amp;#39;s refcount. Nothing keeps the node alive across that window: __dibs_lo_unregister_dmb() removes the node from the hash table under the write lock and immediately frees it. A concurrent final put can therefore free the node between the lookup and the refcount operation: CPU0 (attach)                     CPU1 (owner unregisters) read_lock_bh(&amp;amp;dmb_ht_lock) find dmb_node (refcnt == 1) read_unlock_bh(&amp;amp;dmb_ht_lock)                                   refcount_dec_and_test() 1 -&amp;gt; 0                                   write_lock_bh(&amp;amp;dmb_ht_lock)                                   hash_del(&amp;amp;dmb_node-&amp;gt;list)                                   write_unlock_bh(&amp;amp;dmb_ht_lock)                                   kfree(dmb_node) refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free The same window exists for the refcount_dec_and_test() calls in the detach and unregister paths. Close the race structurally by making hash table membership and the refcount transitions atomic with respect to each other: - Perform the final refcount_dec_and_test() and hash_del() in a single   dmb_ht_lock write-side critical section, in both the unregister and   the detach path. Freeing the node still happens after the…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb() look up the dmb_node under dmb_ht_lock, drop the lock and only then operate on the node&amp;#39;s refcount. Nothing keeps the node alive across that window: __dibs_lo_unregister_dmb() removes the node from the hash table under the write lock and immediately frees it. A concurrent final put can therefore free the node between the lookup and the refcount operation: CPU0 (attach)                     CPU1 (owner unregisters) read_lock_bh(&amp;amp;dmb_ht_lock) find dmb_node (refcnt == 1) read_unlock_bh(&amp;amp;dmb_ht_lock)                                   refcount_dec_and_test() 1 -&amp;gt; 0                                   write_lock_bh(&amp;amp;dmb_ht_lock)                                   hash_del(&amp;amp;dmb_node-&amp;gt;list)                                   write_unlock_bh(&amp;amp;dmb_ht_lock)                                   kfree(dmb_node) refcount_inc_not_zero(&amp;amp;dmb_node-&amp;gt;refcnt)  &amp;lt;-- use-after-free The same window exists for the refcount_dec_and_test() calls in the detach and unregister paths. Close the race structurally by making hash table membership and the refcount transitions atomic with respect to each other: - Perform the final refcount_dec_and_test() and hash_del() in a single   dmb_ht_lock write-side critical section, in both the unregister and   the detach path. Freeing the node still happens after the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74513</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
