CVE-2026-72222
Received Received - Intake

Use-After-Free in Linux Kernel SunRPC TLS Handshake

Vulnerability report for CVE-2026-72222, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback svc_tcp_handshake() stores the raw svc_xprt pointer in tls_handshake_args.ta_data and submits the request through tls_server_hello_x509(). The handshake core takes only sock_hold(req->hr_sk); nothing references the embedding struct svc_sock that svc_tcp_handshake_done() reaches via container_of(). Two close races leave the in-flight callback writing through a freed svc_sock. svc_sock_free() calls tls_handshake_cancel() and discards its return value: a false return means handshake_complete() has already set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not have finished, yet svc_sock_free() proceeds to kfree(svsk). The cancel-loser fall-through inside svc_tcp_handshake() itself produces the same window: when wait_for_completion_interruptible_timeout() returns <= 0 (timeout or signal) and tls_handshake_cancel() returns false, the function does not drain, returns, and svc_handle_xprt() calls svc_xprt_received(), which clears XPT_BUSY and can drop the last reference. A concurrent close then runs svc_sock_free() while svc_tcp_handshake_done() is still updating xpt_flags and walking svsk->sk_handshake_done. The corruption surfaces as set_bit/clear_bit RMW into the freed xpt_flags slab slot and as complete_all() walking and writing the freed wait_queue_head_t list embedded in sk_handshake_done -- a slab-corruption primitive, not a benign read. The path is reachable on any TLS-enabled NFS server whenever a connection close overlaps the tlshd downcall delivery window; the interruptible wait means signal delivery suffices, not just SVC_HANDSHAKE_TO expiry. Take svc_xprt_get(xprt) immediately before tls_server_hello_x509() so the in-flight callback owns its own reference. Release it on the two edges where the callback is guaranteed not to fire -- submission failure from tls_server_hello_x509() and a successful tls_handshake_cancel() -- and at the tail of svc_tcp_handshake_done() after complete_all(). [cel: rewrote commit message to describe the actual change]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-17
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel's SunRPC subsystem when handling asynchronous TLS handshakes. It occurs when a connection close overlaps with the TLS handshake process, causing the kernel to access freed memory. The issue stems from improper reference counting of the svc_xprt transport object during the TLS handshake callback.

Detection Guidance

This vulnerability is specific to Linux kernel versions with the affected RPC-over-TLS code. Detection requires checking kernel version and RPC service configurations. No direct commands are provided in the context to detect this issue. Review kernel logs for slab corruption errors or RPC service crashes during TLS handshake.

Impact Analysis

This vulnerability could allow an attacker to cause a denial-of-service condition or potentially execute arbitrary code on a system running a vulnerable NFS server with TLS enabled. The impact occurs when a connection is closed during the TLS handshake window, leading to memory corruption.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling memory corruption through slab corruption, which may lead to unauthorized data access or system instability. Such issues could compromise data integrity and confidentiality, critical for GDPR and HIPAA compliance.

Mitigation Strategies

Apply the kernel patch that pins the svc_xprt reference during TLS handshake. Update to a fixed Linux kernel version. Disable NFS over TLS if not required. Monitor RPC service stability and kernel logs for signs of corruption.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72222. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart