CVE-2026-64523: net/handshake: Take a long-lived file reference at submit
In the Linux kernel, the following vulnerability has been resolved:
net/handshake: Take a long-lived file reference at submit
handshakenlacceptdoit() needs the file pointer backing req->hrsk->sksocket to survive the window between handshakereqnext() and the subsequent FDPREPARE() and getfile(). The submit-side sockhold() does not provide that. skrefcnt keeps struct sock alive, but struct socket is owned by sock->file: when the consumer fputs the last file reference, sockrelease() tears the socket down regardless of any sockhold.
Add an hrfile pointer to struct handshakereq and acquire an explicit reference on sock->file during handshakereqsubmit(). handshakecomplete() and handshakereqcancel() 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 handshakereqcancel() can discover the request and race the error path. Gate the error-path cleanup -- skdestruct restoration, fput, and request destruction -- with testandsetbit(HANDSHAKEFREQCOMPLETED), the same serialization handshakecomplete() and handshakereqcancel() 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64523?
CVE-2026-64523 has a risk rating of 44.
How do I fix CVE-2026-64523?
To mitigate CVE-2026-64523, ensure you update the Linux kernel to the latest patched version.
What systems are affected by CVE-2026-64523?
CVE-2026-64523 affects systems running vulnerable versions of the Linux kernel.
What kind of vulnerability is CVE-2026-64523?
CVE-2026-64523 is related to a file reference handling issue in the Linux kernel's networking component.
Is CVE-2026-64523 likely to be exploited?
The potential for exploitation of CVE-2026-64523 depends on the specific use cases and configurations of the affected systems.