From: Geliang Tang <geliang@kernel.org>
To: Jiangshan Yi <yijiangshan@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2] selftests: mptcp: diag: fix stack buffer overflow in get_subflow_info()
Date: Thu, 02 Jul 2026 13:50:38 +0800 [thread overview]
Message-ID: <f66bcc626255440b7fc7ef8c2a9b9dde0675f30e.camel@kernel.org> (raw)
In-Reply-To: <20260702041118.2193877-1-yijiangshan@kylinos.cn>
Hi Jiangshan,
On Thu, 2026-07-02 at 12:11 +0800, Jiangshan Yi wrote:
> get_subflow_info() parses the subflow address string with:
>
> char saddr[64], daddr[64];
>
> ret = sscanf(subflow_addrs, "%[^:]:%d %[^:]:%d",
> saddr, &sport, daddr, &dport);
>
> The subflow_addrs buffer holds up to 1024 bytes and is taken directly
> from the command line ("-c" argument). The "%[^:]" conversions have
> no
> maximum field width, so if the address substring before the ':'
> exceeds
> 63 bytes, sscanf() writes past the end of the 64-byte saddr/daddr
> stack
> buffers. This overflows the stack, corrupting adjacent stack data
> such
> as the saved return address, and can crash the tool or lead to
> out-of-bounds writes controlled by user-supplied input.
>
> Bound both string conversions to the destination buffer size by
> adding
> an explicit maximum field width of 63 (leaving room for the
> terminating
> NUL), so at most 63 bytes are written into each 64-byte buffer:
>
> ret = sscanf(subflow_addrs, "%63[^:]:%d %63[^:]:%d",
> saddr, &sport, daddr, &dport);
v2 looks good now.
Reviewed-by: Geliang Tang <geliang@kernel.org>
>
> Fixes: c7ac7452df70 ("selftests: mptcp: add helpers to get
> subflow_info")
I suggest to remove this Fixes tag when applying it. Since this is a
cleanup, not fix.
> Suggested-by: Geliang Tang <geliang@kernel.org>
Also remove this line, add my Reviewed-by tag is enough.
Thanks,
-Geliang
> Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>
> ---
> v2:
> - add field width to sscanf() (fix >80 col warning, MPTCP CI)
> - fix subject prefix: mptcp_diag: -> diag: (Geliang Tang)
>
> tools/testing/selftests/net/mptcp/mptcp_diag.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_diag.c
> b/tools/testing/selftests/net/mptcp/mptcp_diag.c
> index 5e222ba977e4..3b8d2c8a6216 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_diag.c
> +++ b/tools/testing/selftests/net/mptcp/mptcp_diag.c
> @@ -377,7 +377,8 @@ static void get_subflow_info(char *subflow_addrs)
> int ret;
> int fd;
>
> - ret = sscanf(subflow_addrs, "%[^:]:%d %[^:]:%d", saddr,
> &sport, daddr, &dport);
> + ret = sscanf(subflow_addrs, "%63[^:]:%d %63[^:]:%d",
> + saddr, &sport, daddr, &dport);
> if (ret != 4)
> die_perror("IP PORT Pairs has style problems!");
>
next prev parent reply other threads:[~2026-07-02 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 4:11 [PATCH mptcp-next v2] selftests: mptcp: diag: fix stack buffer overflow in get_subflow_info() Jiangshan Yi
2026-07-02 5:14 ` MPTCP CI
2026-07-02 5:50 ` Geliang Tang [this message]
2026-07-02 6:29 ` [PATCH mptcp-next v3] " Jiangshan Yi
2026-07-02 7:37 ` MPTCP CI
2026-07-03 1:09 ` Geliang Tang
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=f66bcc626255440b7fc7ef8c2a9b9dde0675f30e.camel@kernel.org \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=yijiangshan@kylinos.cn \
/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).