net/handshake: Take a long-lived file reference at submit
CVE-2026-64523 · published 25 Jul 2026
How serious is it
- Severity: critical, CVSS score 9.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-64523?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 3b3009ea8abb713b022d94fba95ec270cf6e7eae to < 22e371a93563c30ebebc576db049785e0d7fc617, 3b3009ea8abb713b022d94fba95ec270cf6e7eae to < 685b10dd0e32c7782cead16c8cf055c609678583, 3b3009ea8abb713b022d94fba95ec270cf6e7eae to < b913801ad9b9a51437d84d030ec6843e08976bd6, 3b3009ea8abb713b022d94fba95ec270cf6e7eae to < 16eaba5aa89c04eea125905bb8f988c1897f4f29
- Linux Linux: 6.4
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/22e371a93563c30ebebc576db049785e0d7fc617
- git.kernel.org/stable/c/685b10dd0e32c7782cead16c8cf055c609678583
- git.kernel.org/stable/c/b913801ad9b9a51437d84d030ec6843e08976bd6
- git.kernel.org/stable/c/16eaba5aa89c04eea125905bb8f988c1897f4f29
- git.kernel.org/stable/c/09dba37eee70d0596e26645015f1aa95a9848e9d
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON