<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:24:06.337609+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38552</id>
    <title>CVE-2025-38552 — mptcp: plug races between subflow fail and subflow creation</title>
    <updated>2026-09-30T23:24:06.339149+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mptcp: plug races between subflow fail and subflow creation</p>
<p>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.</p>
<p>The solution is similar. Use a separate flag to track the condition
'socket state prevent any additional subflow creation' protected by the
fallback lock.</p>
<p>The socket fallback makes such flag true, and also receiving or sending
an MP_FAIL option.</p>
<p>The field 'allow_infinite_fallback' is now always touched under the
relevant lock, we can drop the ONCE annotation on write.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38552"/>
  </entry>
</feed>
