<?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>Mon, 05 Oct 2026 17:19:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49669 — mptcp: fix race on unaccepted mptcp sockets</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49669</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: fix race on unaccepted mptcp sockets&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The mptcp socket&amp;#39;s worker can run in the time interval between such delete
operations. When that happens, any access to msk-&amp;gt;first will cause an UaF
access, as the subflow cleanup did not cleared such field in the mptcp
socket.&lt;/p&gt;
&lt;p&gt;Address the issue explicitly traversing the listener socket accept
queue at close time and performing the needed cleanup on the pending
msk.&lt;/p&gt;
&lt;p&gt;Note that the locking is a bit tricky, as we need to acquire the msk
socket lock, while still owning the subflow socket one.&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: fix race on unaccepted mptcp sockets&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The mptcp socket&amp;#39;s worker can run in the time interval between such delete
operations. When that happens, any access to msk-&amp;gt;first will cause an UaF
access, as the subflow cleanup did not cleared such field in the mptcp
socket.&lt;/p&gt;
&lt;p&gt;Address the issue explicitly traversing the listener socket accept
queue at close time and performing the needed cleanup on the pending
msk.&lt;/p&gt;
&lt;p&gt;Note that the locking is a bit tricky, as we need to acquire the msk
socket lock, while still owning the subflow socket one.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49669</guid>
    </item>
  </channel>
</rss>
