From: Matthieu Baerts <matttbe@kernel.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org
Cc: cpaasch@apple.com, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org,
syzbot+ff020673c5e3d94d9478@syzkaller.appspotmail.com
Subject: Re: [PATCH] mptcp: zero opts->ext_copy in mptcp_established_options_dss()
Date: Mon, 4 May 2026 11:37:14 +0200 [thread overview]
Message-ID: <03e9b128-109c-41fb-9147-0cf9b6127d73@kernel.org> (raw)
In-Reply-To: <20260504003156.11125-1-kartikey406@gmail.com>
Hi Deepanshu,
On 04/05/2026 02:31, Deepanshu Kartikey wrote:
> syzbot reported a KMSAN uninit-value in mptcp_write_data_fin() reached
> via tcp_send_ack() from the subflow shutdown path:
>
> BUG: KMSAN: uninit-value in mptcp_write_data_fin net/mptcp/options.c:542
> mptcp_established_options_dss net/mptcp/options.c:590
> mptcp_established_options net/mptcp/options.c:874
> tcp_established_options net/ipv4/tcp_output.c:1192
> __tcp_transmit_skb net/ipv4/tcp_output.c:1575
> __tcp_send_ack net/ipv4/tcp_output.c:4499
> tcp_send_ack net/ipv4/tcp_output.c:4505
> mptcp_subflow_shutdown net/mptcp/protocol.c:3137
> mptcp_check_send_data_fin net/mptcp/protocol.c:3218
> __mptcp_wr_shutdown net/mptcp/protocol.c:3234
> __mptcp_close net/mptcp/protocol.c:3313
>
> Local variable opts created at:
> __tcp_transmit_skb net/ipv4/tcp_output.c:1536
>
> __tcp_transmit_skb() partially clears its on-stack tcp_out_options via
> "memset(&opts.cleared, ...)" which does not cover opts.mptcp, so MPTCP
> is responsible for initializing opts->ext_copy before use.
>
> mptcp_established_options_dss() only writes opts->ext_copy when an
> MPTCP extension is attached to the skb ("opts->ext_copy = *mpext").
> When tcp_send_ack() builds a fresh pure-ACK skb during subflow
> shutdown, the skb has no extension and that assignment is skipped, but
> the function still calls mptcp_write_data_fin(&opts->ext_copy) because
> snd_data_fin_enable is set. mptcp_write_data_fin() then reads
> ext->use_map to choose between writing a synthetic DATA_FIN mapping or
> extending an existing one, and that read hits uninitialized stack
> memory.
>
> Zero opts->ext_copy at the top of mptcp_established_options_dss() so
> mptcp_write_data_fin() takes its synthetic-mapping branch on clean
> memory.
Thank you for sharing this patch!
Kuniyuki already shared the same patch on the MPTCP ML a few days ago:
https://lore.kernel.org/mptcp/20260501061939.1808489-1-kuniyu@google.com/T/#u
A v2 has been shared a few hours ago:
https://lore.kernel.org/mptcp/20260504044051.3725846-1-kuniyu@google.com/T/#u
(and apparently, a v3 will be needed)
Cheers,
Matt
--
pw-bot: Rejected
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-05-04 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 0:31 [PATCH] mptcp: zero opts->ext_copy in mptcp_established_options_dss() Deepanshu Kartikey
2026-05-04 9:37 ` Matthieu Baerts [this message]
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=03e9b128-109c-41fb-9147-0cf9b6127d73@kernel.org \
--to=matttbe@kernel.org \
--cc=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kartikey406@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+ff020673c5e3d94d9478@syzkaller.appspotmail.com \
/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