<?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>Thu, 08 Oct 2026 12:36:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-45009 — mptcp: pm: only decrement add_addr_accepted for MPJ req</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-45009</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;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&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;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-45009</guid>
    </item>
  </channel>
</rss>
