<?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 04:09:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68775 — net/handshake: duplicate handshake cancellations leak socket</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68775</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/handshake: duplicate handshake cancellations leak socket&lt;/p&gt;
&lt;p&gt;When a handshake request is cancelled it is removed from the
handshake_net-&amp;gt;hn_requests list, but it is still present in the
handshake_rhashtbl until it is destroyed.&lt;/p&gt;
&lt;p&gt;If a second cancellation request arrives for the same handshake request,
then remove_pending() will return false... and assuming
HANDSHAKE_F_REQ_COMPLETED isn&amp;#39;t set in req-&amp;gt;hr_flags, we&amp;#39;ll continue
processing through the out_true label, where we put another reference on
the sock and a refcount underflow occurs.&lt;/p&gt;
&lt;p&gt;This can happen for example if a handshake times out - particularly if
the SUNRPC client sends the AUTH_TLS probe to the server but doesn&amp;#39;t
follow it up with the ClientHello due to a problem with tlshd.  When the
timeout is hit on the server, the server will send a FIN, which triggers
a cancellation request via xs_reset_transport().  When the timeout is
hit on the client, another cancellation request happens via
xs_tls_handshake_sync().&lt;/p&gt;
&lt;p&gt;Add a test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED) in the pending cancel
path so duplicate cancels can be detected.&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/handshake: duplicate handshake cancellations leak socket&lt;/p&gt;
&lt;p&gt;When a handshake request is cancelled it is removed from the
handshake_net-&amp;gt;hn_requests list, but it is still present in the
handshake_rhashtbl until it is destroyed.&lt;/p&gt;
&lt;p&gt;If a second cancellation request arrives for the same handshake request,
then remove_pending() will return false... and assuming
HANDSHAKE_F_REQ_COMPLETED isn&amp;#39;t set in req-&amp;gt;hr_flags, we&amp;#39;ll continue
processing through the out_true label, where we put another reference on
the sock and a refcount underflow occurs.&lt;/p&gt;
&lt;p&gt;This can happen for example if a handshake times out - particularly if
the SUNRPC client sends the AUTH_TLS probe to the server but doesn&amp;#39;t
follow it up with the ClientHello due to a problem with tlshd.  When the
timeout is hit on the server, the server will send a FIN, which triggers
a cancellation request via xs_reset_transport().  When the timeout is
hit on the client, another cancellation request happens via
xs_tls_handshake_sync().&lt;/p&gt;
&lt;p&gt;Add a test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED) in the pending cancel
path so duplicate cancels can be detected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68775</guid>
    </item>
  </channel>
</rss>
