<?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>Wed, 30 Sep 2026 03:44:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52974 — net: tls: fix strparser anchor skb leak on offload RX setup failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-52974</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;net: tls: fix strparser anchor skb leak on offload RX setup failure&lt;/p&gt;
&lt;p&gt;When tls_set_device_offload_rx() fails at tls_dev_add(), the error path
calls tls_sw_free_resources_rx() to clean up the SW context that was
initialized by tls_set_sw_offload(). This function calls
tls_sw_release_resources_rx() (which stops the strparser via
tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context),
but never frees the anchor skb that was allocated by alloc_skb(0) in
tls_strp_init().&lt;/p&gt;
&lt;p&gt;Note that tls_sw_free_resources_rx() is exclusively used for this
&amp;#34;failed to start offload&amp;#34; code path, there&amp;#39;s no other caller.&lt;/p&gt;
&lt;p&gt;The leak did not exist before commit 84c61fe1a75b (&amp;#34;tls: rx: do not use
the standard strparser&amp;#34;), because the standard strparser doesn&amp;#39;t try
to pre-allocate an skb.&lt;/p&gt;
&lt;p&gt;The normal close path in tls_sk_proto_close() handles cleanup by calling
tls_sw_strparser_done() (which calls tls_strp_done()) after dropping
the socket lock, because tls_strp_done() does cancel_work_sync() and
the strparser work handler takes the socket lock.&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;net: tls: fix strparser anchor skb leak on offload RX setup failure&lt;/p&gt;
&lt;p&gt;When tls_set_device_offload_rx() fails at tls_dev_add(), the error path
calls tls_sw_free_resources_rx() to clean up the SW context that was
initialized by tls_set_sw_offload(). This function calls
tls_sw_release_resources_rx() (which stops the strparser via
tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context),
but never frees the anchor skb that was allocated by alloc_skb(0) in
tls_strp_init().&lt;/p&gt;
&lt;p&gt;Note that tls_sw_free_resources_rx() is exclusively used for this
&amp;#34;failed to start offload&amp;#34; code path, there&amp;#39;s no other caller.&lt;/p&gt;
&lt;p&gt;The leak did not exist before commit 84c61fe1a75b (&amp;#34;tls: rx: do not use
the standard strparser&amp;#34;), because the standard strparser doesn&amp;#39;t try
to pre-allocate an skb.&lt;/p&gt;
&lt;p&gt;The normal close path in tls_sk_proto_close() handles cleanup by calling
tls_sw_strparser_done() (which calls tls_strp_done()) after dropping
the socket lock, because tls_strp_done() does cancel_work_sync() and
the strparser work handler takes the socket lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-52974</guid>
    </item>
  </channel>
</rss>
