CVEvulnerability
CVE-2025-68775
9.8 CRITICAL
Official page ↗
- Status
- Deferred
- Published
- 2026-01-13
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 9.8 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-662
Description
In the Linux kernel, the following vulnerability has been resolved:
net/handshake: duplicate handshake cancellations leak socket
When a handshake request is cancelled it is removed from the
handshake_net->hn_requests list, but it is still present in the
handshake_rhashtbl until it is destroyed.
If a second cancellation request arrives for the same handshake request,
then remove_pending() will return false... and assuming
HANDSHAKE_F_REQ_COMPLETED isn't set in req->hr_flags, we'll continue
processing through the out_true label, where we put another reference on
the sock and a refcount underflow occurs.
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'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().
Add a test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED) in the pending cancel
path so duplicate cancels can be detected.
Related
Weakness · CWE (1)
- CWE-662 Improper Synchronization weakness
References
- https://git.kernel.org/stable/c/011ae80c49d9bfa5b4336f8bd387cd25c7593663 git.kernel.org
- https://git.kernel.org/stable/c/15564bd67e2975002f2a8e9defee33e321d3183f git.kernel.org
- https://git.kernel.org/stable/c/3c330f1dee3cd92b57e19b9d21dc8ce5970b09be git.kernel.org
- https://git.kernel.org/stable/c/e1641177e7fb48a0a5a06658d4aab51da6656659 git.kernel.org