From: "Yilin Zhang" <yilinzhang@moonshot.ai>
To: "Mat Martineau" <martineau@kernel.org>,
"Matthieu Baerts" <matttbe@kernel.org>
Cc: "Yilin Zhang" <yilinzhang@moonshot.ai>, <netdev@vger.kernel.org>,
<mptcp@lists.linux.dev>,
"Kimi Security Team" <bug-report@moonshot.ai>
Subject: [PATCH] tcp: fastopen: check rsk_drop_req() in tcp_fastopen_create_child()
Date: Wed, 2 Sep 2026 20:12:47 +0800 [thread overview]
Message-ID: <20260902121247.3248539-1-yilinzhang@moonshot.ai> (raw)
subflow_syn_recv_sock() destroys the freshly cloned child for an MP_JOIN
SYN under the fatal fallback and hands it back with drop_req=true to
tell the caller to drop both the request and the child. Of the three
syn_recv_sock() callers, tcp_check_req() and the cookie path honor that
contract; tcp_fastopen_create_child() only checks child != NULL.
With an MPTCP listener and server-side Fast Open enabled, this can
become a use-after-free:
1. fetch a TFO cookie,
2. complete a normal MP_CAPABLE handshake to learn the server's key
and compute the token offline,
3. send an MP_JOIN SYN carrying that token and the valid TFO cookie,
4. a subsequent accept() hands the freed socket to userspace, and
any fd operation triggers slab-use-after-free, leading to a
denial of service.
Fixes: 90bf45134d55 ("mptcp: add new sock flag to deal with join subflows")
Reported-by: Kimi Security Team <bug-report@moonshot.ai>
Signed-off-by: Yilin Zhang <yilinzhang@moonshot.ai>
---
net/ipv4/tcp_fastopen.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/ipv4/tcp_fastopen.c b/net/ipv4/tcp_fastopen.c
index 6a031a1a6c9f..7a0b58b39a2c 100644
--- a/net/ipv4/tcp_fastopen.c
+++ b/net/ipv4/tcp_fastopen.c
@@ -337,6 +337,11 @@ static struct sock *tcp_fastopen_create_child(struct sock *sk,
if (!child)
return NULL;
+ if (own_req && rsk_drop_req(req)) {
+ sock_put(child);
+ return NULL;
+ }
+
spin_lock(&queue->fastopenq.lock);
queue->fastopenq.qlen++;
spin_unlock(&queue->fastopenq.lock);
--
2.43.0
next reply other threads:[~2026-09-02 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:12 Yilin Zhang [this message]
2026-09-02 14:12 ` [PATCH] tcp: fastopen: check rsk_drop_req() in tcp_fastopen_create_child() Jiayuan Chen
2026-09-02 15:31 ` Matthieu Baerts
[not found] <c4d4d8c-34af-4ea8-ace8-e10e547d6744@kernel.org>
2026-09-03 7:06 ` Yilin Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260902121247.3248539-1-yilinzhang@moonshot.ai \
--to=yilinzhang@moonshot.ai \
--cc=bug-report@moonshot.ai \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).