SUNRPC: wait for in-flight client TLS handshake callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: wait for in-flight client TLS handshake callback
xs_tls_handshake_sync() gives xs_tls_handshake_done() a reference to the lower transport before submitting the handshake request. On timeout or signal, the synchronous waiter drops that reference after calling tls_handshake_cancel().
handshake_req_cancel() returns false when handshake_complete() has already marked the request complete. In that case the completion callback can still be running, so dropping the callback-owned reference in the waiter can free the lower transport before xs_tls_handshake_done() stores xprt_err or drops its own reference.
If cancellation loses to completion, wait until xs_tls_handshake_done() signals handshake_done and let the callback release its reference. This mirrors the server-side handshake lifetime handling and keeps the timeout or signal return value unchanged.
From the CVE record · Linux
The Linux kernel’s SUNRPC client TLS handshake can free a transport while its completion callback is still using it. This can happen when a timeout or signal triggers cancellation just as the handshake completes. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels that use SUNRPC client TLS handshakes should check their kernel versions against the vendor advisory; affected versions were not provided.