From: Len Baker <len.baker@gmx.com>
To: Kees Cook <keescook@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Len Baker" <len.baker@gmx.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Russell King" <rmk+kernel@armlinux.org.uk>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-hardening@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] drivers/input: Remove all strcpy() uses in favor of strscpy()
Date: Sun, 1 Aug 2021 16:43:16 +0200 [thread overview]
Message-ID: <20210801144316.12841-1-len.baker@gmx.com> (raw)
strcpy() performs no bounds checking on the destination buffer. This
could result in linear overflows beyond the end of the buffer, leading
to all kinds of misbehaviors. The safe replacement is strscpy().
Signed-off-by: Len Baker <len.baker@gmx.com>
---
This is a task of the KSPP [1]
[1] https://github.com/KSPP/linux/issues/88
drivers/input/keyboard/locomokbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/locomokbd.c b/drivers/input/keyboard/locomokbd.c
index dae053596572..dbb3dc48df12 100644
--- a/drivers/input/keyboard/locomokbd.c
+++ b/drivers/input/keyboard/locomokbd.c
@@ -254,7 +254,7 @@ static int locomokbd_probe(struct locomo_dev *dev)
locomokbd->suspend_jiffies = jiffies;
locomokbd->input = input_dev;
- strcpy(locomokbd->phys, "locomokbd/input0");
+ strscpy(locomokbd->phys, "locomokbd/input0", sizeof(locomokbd->phys));
input_dev->name = "LoCoMo keyboard";
input_dev->phys = locomokbd->phys;
--
2.25.1
next reply other threads:[~2021-08-01 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 14:43 Len Baker [this message]
2021-08-01 15:00 ` [PATCH] drivers/input: Remove all strcpy() uses in favor of strscpy() Russell King (Oracle)
2021-08-01 15:57 ` Len Baker
2021-08-01 16:44 ` Kees Cook
2021-08-01 17:19 ` Dmitry Torokhov
2021-08-02 16:17 ` Kees Cook
2021-08-03 7:07 ` Kees Cook
2021-08-03 7:18 ` Hans Verkuil
2021-08-07 14:02 ` Len Baker
2021-08-07 15:17 ` Joe Perches
2021-08-08 11:30 ` Len Baker
2021-08-01 16:39 ` Joe Perches
2021-08-01 16:55 ` Joe Perches
2021-08-02 16:13 ` Kees Cook
2021-08-02 18:57 ` Joe Perches
2021-08-07 14:10 ` Len Baker
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=20210801144316.12841-1-len.baker@gmx.com \
--to=len.baker@gmx.com \
--cc=dmitry.torokhov@gmail.com \
--cc=keescook@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=u.kleine-koenig@pengutronix.de \
/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).