<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T13:15:32.661331+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2021-47132</id>
    <title>CVE-2021-47132 — mptcp: fix sk_forward_memory corruption on retransmission</title>
    <updated>2026-10-08T13:15:32.676918+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mptcp: fix sk_forward_memory corruption on retransmission</p>
<p>MPTCP sk_forward_memory handling is a bit special, as such field
is protected by the msk socket spin_lock, instead of the plain
socket lock.</p>
<p>Currently we have a code path updating such field without handling
the relevant lock:</p>
<p>__mptcp_retrans() -&gt; __mptcp_clean_una_wakeup()</p>
<p>Several helpers in __mptcp_clean_una_wakeup() will update
sk_forward_alloc, possibly causing such field corruption, as reported
by Matthieu.</p>
<p>Address the issue providing and using a new variant of blamed function
which explicitly acquires the msk spin lock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-47132"/>
  </entry>
</feed>
