<?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>Sat, 03 Oct 2026 12:14:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63979 — net/handshake: hand off the pinned file reference to accept_doit</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63979</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: hand off the pinned file reference to accept_doit&lt;/p&gt;
&lt;p&gt;handshake_req_next() removes the request from the per-net
pending list and drops hn_lock before handshake_nl_accept_doit()
reads req-&amp;gt;hr_sk-&amp;gt;sk_socket and dereferences sock-&amp;gt;file (once in
FD_PREPARE() and again in get_file()).  In that window a
consumer running tls_handshake_cancel() followed by sockfd_put()
(svc_sock_free) or __fput_sync() (xs_reset_transport) releases
sock-&amp;gt;file.  sock_release() then runs sock_orphan(), zeroing
sk_socket, and frees the struct socket.  The accept-side code
either reads NULL through sk_socket or chases freed memory.&lt;/p&gt;
&lt;p&gt;The submit-side sock_hold() does not prevent this.  sk_refcnt
protects struct sock, but struct socket and sock-&amp;gt;file are
independently refcounted via the file descriptor the consumer
owns.  Pinning sk leaves sock and sock-&amp;gt;file unprotected.&lt;/p&gt;
&lt;p&gt;Retarget the accept-side dereferences at req-&amp;gt;hr_file, which was
pinned at submit time, instead of req-&amp;gt;hr_sk-&amp;gt;sk_socket-&amp;gt;file.
Pinning on its own is not sufficient: a consumer that cancels
between handshake_req_next() returning and accept_doit reaching
FD_PREPARE() takes the !remove_pending() branch in
handshake_req_cancel() and drops hr_file before the accept side
takes its own reference.  Hand off an additional file reference
inside handshake_req_next(), under hn_lock, so the accept side
operates on a reference that no concurrent handshake_req_cancel()
can…&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: hand off the pinned file reference to accept_doit&lt;/p&gt;
&lt;p&gt;handshake_req_next() removes the request from the per-net
pending list and drops hn_lock before handshake_nl_accept_doit()
reads req-&amp;gt;hr_sk-&amp;gt;sk_socket and dereferences sock-&amp;gt;file (once in
FD_PREPARE() and again in get_file()).  In that window a
consumer running tls_handshake_cancel() followed by sockfd_put()
(svc_sock_free) or __fput_sync() (xs_reset_transport) releases
sock-&amp;gt;file.  sock_release() then runs sock_orphan(), zeroing
sk_socket, and frees the struct socket.  The accept-side code
either reads NULL through sk_socket or chases freed memory.&lt;/p&gt;
&lt;p&gt;The submit-side sock_hold() does not prevent this.  sk_refcnt
protects struct sock, but struct socket and sock-&amp;gt;file are
independently refcounted via the file descriptor the consumer
owns.  Pinning sk leaves sock and sock-&amp;gt;file unprotected.&lt;/p&gt;
&lt;p&gt;Retarget the accept-side dereferences at req-&amp;gt;hr_file, which was
pinned at submit time, instead of req-&amp;gt;hr_sk-&amp;gt;sk_socket-&amp;gt;file.
Pinning on its own is not sufficient: a consumer that cancels
between handshake_req_next() returning and accept_doit reaching
FD_PREPARE() takes the !remove_pending() branch in
handshake_req_cancel() and drops hr_file before the accept side
takes its own reference.  Hand off an additional file reference
inside handshake_req_next(), under hn_lock, so the accept side
operates on a reference that no concurrent handshake_req_cancel()
can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63979</guid>
    </item>
  </channel>
</rss>
