<?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 07:06:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-44991 — tcp: prevent concurrent execution of tcp_sk_exit_batch</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-44991</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;tcp: prevent concurrent execution of tcp_sk_exit_batch&lt;/p&gt;
&lt;p&gt;Its possible that two threads call tcp_sk_exit_batch() concurrently,
once from the cleanup_net workqueue, once from a task that failed to clone
a new netns.  In the latter case, error unwinding calls the exit handlers
in reverse order for the &amp;#39;failed&amp;#39; netns.&lt;/p&gt;
&lt;p&gt;tcp_sk_exit_batch() calls tcp_twsk_purge().
Problem is that since commit b099ce2602d8 (&amp;#34;net: Batch inet_twsk_purge&amp;#34;),
this function picks up twsk in any dying netns, not just the one passed
in via exit_batch list.&lt;/p&gt;
&lt;p&gt;This means that the error unwind of setup_net() can &amp;#34;steal&amp;#34; and destroy
timewait sockets belonging to the exiting netns.&lt;/p&gt;
&lt;p&gt;This allows the netns exit worker to proceed to call&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!refcount_dec_and_test(&amp;amp;net-&amp;gt;ipv4.tcp_death_row.tw_refcount));&lt;/p&gt;
&lt;p&gt;without the expected 1 -&amp;gt; 0 transition, which then splats.&lt;/p&gt;
&lt;p&gt;At same time, error unwind path that is also running inet_twsk_purge()
will splat as well:&lt;/p&gt;
&lt;p&gt;WARNING: .. at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210
...
 refcount_dec include/linux/refcount.h:351 [inline]
 inet_twsk_kill+0x758/0x9c0 net/ipv4/inet_timewait_sock.c:70
 inet_twsk_deschedule_put net/ipv4/inet_timewait_sock.c:221
 inet_twsk_purge+0x725/0x890 net/ipv4/inet_timewait_sock.c:304
 tcp_sk_exit_batch+0x1c/0x170 net/ipv4/tcp_ipv4.c:3522
 ops_exit_list+0x128/0x180 net/core/net_namespace.c:178
 setup_net+0x714/0xb40 net/core/net_namespace.c:375
 copy_net_ns+0x2f0/0x67…&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;tcp: prevent concurrent execution of tcp_sk_exit_batch&lt;/p&gt;
&lt;p&gt;Its possible that two threads call tcp_sk_exit_batch() concurrently,
once from the cleanup_net workqueue, once from a task that failed to clone
a new netns.  In the latter case, error unwinding calls the exit handlers
in reverse order for the &amp;#39;failed&amp;#39; netns.&lt;/p&gt;
&lt;p&gt;tcp_sk_exit_batch() calls tcp_twsk_purge().
Problem is that since commit b099ce2602d8 (&amp;#34;net: Batch inet_twsk_purge&amp;#34;),
this function picks up twsk in any dying netns, not just the one passed
in via exit_batch list.&lt;/p&gt;
&lt;p&gt;This means that the error unwind of setup_net() can &amp;#34;steal&amp;#34; and destroy
timewait sockets belonging to the exiting netns.&lt;/p&gt;
&lt;p&gt;This allows the netns exit worker to proceed to call&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!refcount_dec_and_test(&amp;amp;net-&amp;gt;ipv4.tcp_death_row.tw_refcount));&lt;/p&gt;
&lt;p&gt;without the expected 1 -&amp;gt; 0 transition, which then splats.&lt;/p&gt;
&lt;p&gt;At same time, error unwind path that is also running inet_twsk_purge()
will splat as well:&lt;/p&gt;
&lt;p&gt;WARNING: .. at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210
...
 refcount_dec include/linux/refcount.h:351 [inline]
 inet_twsk_kill+0x758/0x9c0 net/ipv4/inet_timewait_sock.c:70
 inet_twsk_deschedule_put net/ipv4/inet_timewait_sock.c:221
 inet_twsk_purge+0x725/0x890 net/ipv4/inet_timewait_sock.c:304
 tcp_sk_exit_batch+0x1c/0x170 net/ipv4/tcp_ipv4.c:3522
 ops_exit_list+0x128/0x180 net/core/net_namespace.c:178
 setup_net+0x714/0xb40 net/core/net_namespace.c:375
 copy_net_ns+0x2f0/0x67…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-44991</guid>
    </item>
  </channel>
</rss>
