Bug 2507122 (CVE-2026-64523) - CVE-2026-64523 kernel: net/handshake: Take a long-lived file reference at submit
Summary: CVE-2026-64523 kernel: net/handshake: Take a long-lived file reference at submit
Keywords:
Status: NEW
Alias: CVE-2026-64523
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-25 10:06 UTC by OSIDB Bzimport
Modified: 2026-11-10 11:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:90365 0 None None None 2026-10-26 21:02:46 UTC
Red Hat Product Errata RHSA-2026:91565 0 None None None 2026-10-28 03:11:52 UTC
Red Hat Product Errata RHSA-2026:97040 0 None None None 2026-11-10 11:55:35 UTC

Description OSIDB Bzimport 2026-07-25 10:06:12 UTC
In the Linux kernel, the following vulnerability has been resolved:

net/handshake: Take a long-lived file reference at submit

handshake_nl_accept_doit() needs the file pointer backing
req->hr_sk->sk_socket to survive the window between
handshake_req_next() and the subsequent FD_PREPARE() and get_file().
The submit-side sock_hold() does not provide that.  sk_refcnt keeps
struct sock alive, but struct socket is owned by sock->file: when
the consumer fputs the last file reference, sock_release() tears
the socket down regardless of any sock_hold.

Add an hr_file pointer to struct handshake_req and acquire an
explicit reference on sock->file during handshake_req_submit().
handshake_complete() and handshake_req_cancel() release the
reference on the completion-bit-winning path.

The submit error path must also release the file reference, but
after rhashtable insertion a concurrent handshake_req_cancel() can
discover the request and race the error path.  Gate the error-path
cleanup -- sk_destruct restoration, fput, and request destruction
-- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same
serialization handshake_complete() and handshake_req_cancel()
already use.  When cancel has already claimed ownership, the submit
error path returns without touching the request; socket teardown
handles final destruction.

The accept-side dereferences are not yet retargeted; that change
comes in the next patch.

Comment 4 Jon Orris 2026-10-26 21:02:45 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:90365 https://access.redhat.com/errata/RHSA-2026:90365

Comment 6 Jon Orris 2026-10-28 03:11:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:91565 https://access.redhat.com/errata/RHSA-2026:91565

Comment 7 errata-xmlrpc 2026-11-10 11:55:34 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:97040 https://access.redhat.com/errata/RHSA-2026:97040


Note You need to log in before you can comment on or make changes to this bug.