CVE-2026-99603: mptcp: pm: kernel: use RCU to free endpoint listeners
In the Linux kernel, the following vulnerability has been resolved:
mptcp: pm: kernel: use RCU to free endpoint listeners
mptcppmnlcreatelistensocket() starts the TCP listener directly instead of going through mptcplisten(). It consequently misses setting SOCKRCUFREE on the parent MPTCP socket.
tcpchildprocess() can invoke the listener's subflowdataready() callback without holding the MPTCP parent lock or a reference to the parent. An authenticated MPJOIN racing with endpoint teardown can therefore access the parent after its last reference has been dropped. The ADDADDR error path can also close an already published listener.
Set SOCKRCUFREE before inetlistensk() publishes the TCP listener, matching mptcplisten(). This protects the parent on every subsequent close path, including a failed endpoint addition.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Compensating control
In mptcp_pm_nl_create_listen_socket(), set SOCK_RCU_FREE on the parent MPTCP socket before __inet_listen_sk() publishes the TCP listener.
Frequently Asked Questions
What conditions are required to trigger this issue?
An authenticated MP_JOIN must race with teardown of an MPTCP endpoint listener. The affected path involves endpoint listeners created by the kernel MPTCP path, including a failure while adding an ADD_ADDR endpoint.
Is a normal TCP listener affected?
The described issue is specific to MPTCP endpoint listeners created through mptcp_pm_nl_create_listen_socket(). It results from that path not setting SOCK_RCU_FREE on the parent MPTCP socket before publishing the TCP listener.
What is the practical effect of a successful race?
The listener's subflow_data_ready() callback can access the MPTCP parent after the parent's final reference has been dropped. This is a use-after-free condition during concurrent MP_JOIN handling and endpoint teardown.
What change resolves the issue?
The fix sets SOCK_RCU_FREE before __inet_listen_sk() publishes the TCP listener. This protects the MPTCP parent on later listener-close paths, including failed endpoint-addition cleanup.