<?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-05T18:48:17.177441+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-2022-49669</id>
    <title>CVE-2022-49669 — mptcp: fix race on unaccepted mptcp sockets</title>
    <updated>2026-10-05T18:48:17.193883+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 race on unaccepted mptcp sockets</p>
<p>When the listener socket owning the relevant request is closed,
it frees the unaccepted subflows and that causes later deletion
of the paired MPTCP sockets.</p>
<p>The mptcp socket's worker can run in the time interval between such delete
operations. When that happens, any access to msk-&gt;first will cause an UaF
access, as the subflow cleanup did not cleared such field in the mptcp
socket.</p>
<p>Address the issue explicitly traversing the listener socket accept
queue at close time and performing the needed cleanup on the pending
msk.</p>
<p>Note that the locking is a bit tricky, as we need to acquire the msk
socket lock, while still owning the subflow socket one.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2022-49669"/>
  </entry>
</feed>
