<?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>Wed, 30 Sep 2026 23:24:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38552 — mptcp: plug races between subflow fail and subflow creation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38552</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: plug races between subflow fail and subflow creation&lt;/p&gt;
&lt;p&gt;We have races similar to the one addressed by the previous patch between
subflow failing and additional subflow creation. They are just harder to
trigger.&lt;/p&gt;
&lt;p&gt;The solution is similar. Use a separate flag to track the condition
&amp;#39;socket state prevent any additional subflow creation&amp;#39; protected by the
fallback lock.&lt;/p&gt;
&lt;p&gt;The socket fallback makes such flag true, and also receiving or sending
an MP_FAIL option.&lt;/p&gt;
&lt;p&gt;The field &amp;#39;allow_infinite_fallback&amp;#39; is now always touched under the
relevant lock, we can drop the ONCE annotation on write.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: plug races between subflow fail and subflow creation&lt;/p&gt;
&lt;p&gt;We have races similar to the one addressed by the previous patch between
subflow failing and additional subflow creation. They are just harder to
trigger.&lt;/p&gt;
&lt;p&gt;The solution is similar. Use a separate flag to track the condition
&amp;#39;socket state prevent any additional subflow creation&amp;#39; protected by the
fallback lock.&lt;/p&gt;
&lt;p&gt;The socket fallback makes such flag true, and also receiving or sending
an MP_FAIL option.&lt;/p&gt;
&lt;p&gt;The field &amp;#39;allow_infinite_fallback&amp;#39; is now always touched under the
relevant lock, we can drop the ONCE annotation on write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38552</guid>
    </item>
  </channel>
</rss>
