<?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>Tue, 29 Sep 2026 02:01:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97524 — mptcp: avoid unneeded actions on subflow reset</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97524</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: avoid unneeded actions on subflow reset&lt;/p&gt;
&lt;p&gt;Once in a blue moon, the mptcp receive path can recursively call
mptcp_data_ready() via state change under unlucky error conditions, and
then try to hold the data lock again.&lt;/p&gt;
&lt;p&gt;Break the recursion loop explicitly checking for the exceptional
condition.&lt;/p&gt;
&lt;p&gt;Add a new flag instead of using an existing one like &amp;#39;closing&amp;#39;, to exit
early in subflow_state_change(), and explicitly flush the RX queue at
reset time.&lt;/p&gt;
&lt;p&gt;This avoids unneeded processing to check for available data -- calling
get_mapping_status() and more on a dying subflow -- but also in error
reporting and worker scheduling.&lt;/p&gt;
&lt;p&gt;Note that we must consume the currently peeked skb before invoking
mptcp_dss_corruption to avoid consuming it again after the eventual
reset has freed it.&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: avoid unneeded actions on subflow reset&lt;/p&gt;
&lt;p&gt;Once in a blue moon, the mptcp receive path can recursively call
mptcp_data_ready() via state change under unlucky error conditions, and
then try to hold the data lock again.&lt;/p&gt;
&lt;p&gt;Break the recursion loop explicitly checking for the exceptional
condition.&lt;/p&gt;
&lt;p&gt;Add a new flag instead of using an existing one like &amp;#39;closing&amp;#39;, to exit
early in subflow_state_change(), and explicitly flush the RX queue at
reset time.&lt;/p&gt;
&lt;p&gt;This avoids unneeded processing to check for available data -- calling
get_mapping_status() and more on a dying subflow -- but also in error
reporting and worker scheduling.&lt;/p&gt;
&lt;p&gt;Note that we must consume the currently peeked skb before invoking
mptcp_dss_corruption to avoid consuming it again after the eventual
reset has freed it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97524</guid>
    </item>
  </channel>
</rss>
