<?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>Fri, 02 Oct 2026 18:34:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74401 — dlm: fix add msg handle in send_queue ordered</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74401</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;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;&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;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://vulnerability.circl.lu/vuln/cve-2026-74401</guid>
    </item>
  </channel>
</rss>
