From: Peter Hutterer <peter.hutterer@who-t.net>
To: Jason Gerecke <killertofu@gmail.com>
Cc: linux-input@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Ping Cheng <pinglinux@gmail.com>,
Aaron Armstrong Skomra <skomra@gmail.com>,
Joshua Dickens <Joshua@joshua-dickens.com>,
Jason Gerecke <jason.gerecke@wacom.com>,
Ping Cheng <ping.cheng@wacom.com>
Subject: Re: [PATCH] HID: wacom: Check for string overflow from strscpy calls
Date: Thu, 4 May 2023 14:34:42 +1000 [thread overview]
Message-ID: <20230504043442.GB1129520@quokka> (raw)
In-Reply-To: <20230414182210.383218-1-jason.gerecke@wacom.com>
On Fri, Apr 14, 2023 at 11:22:10AM -0700, Jason Gerecke wrote:
> From: Jason Gerecke <killertofu@gmail.com>
>
> The strscpy function is able to return an error code when a copy would
> overflow the size of the destination. The copy is stopped and the buffer
> terminated before overflow actually occurs so it is safe to continue
> execution, but we should still produce a warning should this occur.
>
> Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
> Reviewed-by: Ping Cheng <ping.cheng@wacom.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Cheers,
Peter
> ---
> drivers/hid/wacom_sys.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/hid/wacom_sys.c b/drivers/hid/wacom_sys.c
> index 8214896adadad..7192970d199a0 100644
> --- a/drivers/hid/wacom_sys.c
> +++ b/drivers/hid/wacom_sys.c
> @@ -2224,7 +2224,9 @@ static void wacom_update_name(struct wacom *wacom, const char *suffix)
> } else if (strstr(product_name, "Wacom") ||
> strstr(product_name, "wacom") ||
> strstr(product_name, "WACOM")) {
> - strscpy(name, product_name, sizeof(name));
> + if (strscpy(name, product_name, sizeof(name)) < 0) {
> + hid_warn(wacom->hdev, "String overflow while assembling device name");
> + }
> } else {
> snprintf(name, sizeof(name), "Wacom %s", product_name);
> }
> @@ -2242,7 +2244,9 @@ static void wacom_update_name(struct wacom *wacom, const char *suffix)
> if (name[strlen(name)-1] == ' ')
> name[strlen(name)-1] = '\0';
> } else {
> - strscpy(name, features->name, sizeof(name));
> + if (strscpy(name, features->name, sizeof(name)) < 0) {
> + hid_warn(wacom->hdev, "String overflow while assembling device name");
> + }
> }
>
> snprintf(wacom_wac->name, sizeof(wacom_wac->name), "%s%s",
> @@ -2500,8 +2504,10 @@ static void wacom_wireless_work(struct work_struct *work)
> goto fail;
> }
>
> - strscpy(wacom_wac->name, wacom_wac1->name,
> - sizeof(wacom_wac->name));
> + if (strscpy(wacom_wac->name, wacom_wac1->name,
> + sizeof(wacom_wac->name)) < 0) {
> + hid_warn(wacom->hdev, "String overflow while assembling device name");
> + }
> }
>
> return;
> --
> 2.40.0
>
next prev parent reply other threads:[~2023-05-04 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 18:22 [PATCH] HID: wacom: Check for string overflow from strscpy calls Jason Gerecke
2023-04-28 17:32 ` Jason Gerecke
2023-05-04 4:34 ` Peter Hutterer [this message]
2023-05-17 16:51 ` Jason Gerecke
2023-05-23 13:07 ` Jiri Kosina
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=20230504043442.GB1129520@quokka \
--to=peter.hutterer@who-t.net \
--cc=Joshua@joshua-dickens.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jason.gerecke@wacom.com \
--cc=jikos@kernel.org \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=ping.cheng@wacom.com \
--cc=pinglinux@gmail.com \
--cc=skomra@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