<?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:02:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74401</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74401</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74401</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1203 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</link>
      <description>certfr-2026-avi-1203</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</guid>
    </item>
    <item>
      <title>EUVD-2026-354210</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354210</link>
      <description>EUVD-2026-354210</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354210</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74401</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74401</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dlm: fix add msg handle in send_queue ordered&lt;/p&gt;
&lt;p&gt;In a benchmark scenario triggering a lot of requests that triggers a lot
of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered
according the oldest seq number. This ordering is required by
dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older
sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;.&lt;/p&gt;
&lt;p&gt;The side effects of not having it correct ordered regarding
&amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free.&lt;/p&gt;
&lt;p&gt;I only was able to reproduce this issue in a experimental DLM branch
and a user space DLM benchmark that uses io_uring. After changing this I
don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&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;dlm: fix add msg handle in send_queue ordered&lt;/p&gt;
&lt;p&gt;In a benchmark scenario triggering a lot of requests that triggers a lot
of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered
according the oldest seq number. This ordering is required by
dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older
sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;.&lt;/p&gt;
&lt;p&gt;The side effects of not having it correct ordered regarding
&amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free.&lt;/p&gt;
&lt;p&gt;I only was able to reproduce this issue in a experimental DLM branch
and a user space DLM benchmark that uses io_uring. After changing this I
don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74401</guid>
    </item>
    <item>
      <title>GHSA-wgc9-j6gh-934m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wgc9-j6gh-934m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dlm: fix add msg handle in send_queue ordered&lt;/p&gt;
&lt;p&gt;In a benchmark scenario triggering a lot of requests that triggers a lot
of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered
according the oldest seq number. This ordering is required by
dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older
sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;.&lt;/p&gt;
&lt;p&gt;The side effects of not having it correct ordered regarding
&amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free.&lt;/p&gt;
&lt;p&gt;I only was able to reproduce this issue in a experimental DLM branch
and a user space DLM benchmark that uses io_uring. After changing this I
don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&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;dlm: fix add msg handle in send_queue ordered&lt;/p&gt;
&lt;p&gt;In a benchmark scenario triggering a lot of requests that triggers a lot
of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered
according the oldest seq number. This ordering is required by
dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older
sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;.&lt;/p&gt;
&lt;p&gt;The side effects of not having it correct ordered regarding
&amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free.&lt;/p&gt;
&lt;p&gt;I only was able to reproduce this issue in a experimental DLM branch
and a user space DLM benchmark that uses io_uring. After changing this I
don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wgc9-j6gh-934m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74401</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74401</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dlm: fix add msg handle in send_queue ordered In a benchmark scenario triggering a lot of requests that triggers a lot of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered according the oldest seq number. This ordering is required by dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;. The side effects of not having it correct ordered regarding &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free. I only was able to reproduce this issue in a experimental DLM branch and a user space DLM benchmark that uses io_uring. After changing this I don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dlm: fix add msg handle in send_queue ordered In a benchmark scenario triggering a lot of requests that triggers a lot of DLM messages on the network it can be that the mh-&amp;gt;seq is not ordered according the oldest seq number. This ordering is required by dlm_receive_ack as &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; will stop to check for older sequence numbers that are ordered in the tail of &amp;#34;node-&amp;gt;send_queue&amp;#34;. The side effects of not having it correct ordered regarding &amp;#34;before(mh-&amp;gt;seq, seq)&amp;#34; are refcounting issues and use-after free. I only was able to reproduce this issue in a experimental DLM branch and a user space DLM benchmark that uses io_uring. After changing this I don&amp;#39;t experienced any refcounting with the sending buffer issues anymore.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74401</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>
