From: Franco Martelli <martellif67@gmail.com>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>,
masahiroy@kernel.org, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
Franco Martelli <martellif67@gmail.com>
Subject: Re: [PATCH] kconfig/lxdialog: replace strcpy() with strscpy() in inputbox.c
Date: Fri, 25 Jul 2025 11:53:40 +0200 [thread overview]
Message-ID: <f020e62b-5186-4461-8fe9-de64d35de488@gmail.com> (raw)
In-Reply-To: <20250725055928.37658-1-suchitkarunakaran@gmail.com>
On 25/07/25 at 07:59, Suchit Karunakaran wrote:
> strcpy() performs no bounds checking and can lead to buffer overflows if
> the input string exceeds the destination buffer size. Replace it with
> strscpy(), which ensures the input is always NULL-terminated and
> prevents overflows.
>
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
> ---
> scripts/kconfig/lxdialog/inputbox.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/kconfig/lxdialog/inputbox.c b/scripts/kconfig/lxdialog/inputbox.c
> index 3c6e24b20f5b..8880ccaffa0b 100644
> --- a/scripts/kconfig/lxdialog/inputbox.c
> +++ b/scripts/kconfig/lxdialog/inputbox.c
> @@ -40,7 +40,7 @@ int dialog_inputbox(const char *title, const char *prompt, int height, int width
> if (!init)
> instr[0] = '\0';
> else
> - strcpy(instr, init);
> + strscpy(instr, init, MAX_LEN + 1);
>
> do_resize:
> if (getmaxy(stdscr) <= (height - INPUTBOX_HEIGHT_MIN))
perhaps it's better to sanitize the whole code in
script/kconfig not only in lxdialog/inputbox.c
$ grep -Rn strcpy scripts/kconfig/*
scripts/kconfig/confdata.c:143: strcpy(depfile_path +
depfile_prefix_len, name);
scripts/kconfig/lxdialog/util.c:348: strcpy(tempstr, prompt);
scripts/kconfig/lxdialog/inputbox.c:43: strcpy(instr, init);
scripts/kconfig/symbol.c:764: strcpy(val, newval);
scripts/kconfig/util.c:55: strcpy(gs.s, "\0");
because the script "checkpatch.pl" emits a warning
whether strcpy() function is used:
WARNING: Prefer strscpy over strcpy - see:
https://github.com/KSPP/linux/issues/88
Kind regards,
--
Franco Martelli
next prev parent reply other threads:[~2025-07-25 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 5:59 Suchit Karunakaran
2025-07-25 9:53 ` Franco Martelli [this message]
2025-07-25 10:11 ` Suchit K
2025-07-25 13:00 ` Nicolas Schier
2025-07-25 14:36 ` Suchit K
2025-07-26 16:59 ` Nicolas Schier
2025-07-26 17:06 ` Suchit K
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=f020e62b-5186-4461-8fe9-de64d35de488@gmail.com \
--to=martellif67@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=suchitkarunakaran@gmail.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
all inboxes | Powered by JetHome®