From: Pavel Skripkin <paskripkin@gmail.com>
To: Charlie Sands <sandsch@northvilleschools.net>,
gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Fix unsafe memory access by memcmp
Date: Mon, 4 Apr 2022 19:33:01 +0300 [thread overview]
Message-ID: <c14c23a0-6b0b-04b3-e58d-786c77726874@gmail.com> (raw)
In-Reply-To: <YkpdVyuQguGzPSNE@sckzor-linux.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]
Hi Charlie,
On 4/4/22 05:52, Charlie Sands wrote:
> This patch fixes sparse warnings about the memcmp function unsafely
> accessing userspace memory without first copying it to kernel space.
>
> Signed-off-by: Charlie Sands <sandsch@northvilleschools.net>
> ---
>
> V2: Fixed checkpatch.pl warning and changed variable name as suggested
> by Greg K. H. and improved error checking on the "copy_from_user" function as
> suggested by Pavel Skripkin.
>
You did not improved error handling of copy_from_user() as I suggested.
if (expr) and if (expr != 0) are exactly the same
> drivers/staging/r8188eu/os_dep/ioctl_linux.c | 21 ++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/os_dep/ioctl_linux.c b/drivers/staging/r8188eu/os_dep/ioctl_linux.c
> index 7df213856d66..4b4eec2bde96 100644
> --- a/drivers/staging/r8188eu/os_dep/ioctl_linux.c
> +++ b/drivers/staging/r8188eu/os_dep/ioctl_linux.c
> @@ -3233,23 +3233,28 @@ static int rtw_p2p_get(struct net_device *dev,
> struct iw_request_info *info,
> union iwreq_data *wrqu, char *extra)
> {
> - if (!memcmp(wrqu->data.pointer, "status", 6)) {
> + char wrqu_data[9];
> +
> + if (copy_from_user(wrqu_data, wrqu->data.pointer, 9) != 0)
> + return 0;
> +
I've suggested to return -EFAULT here
With regards,
Pavel Skripkin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2022-04-04 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 2:52 Charlie Sands
2022-04-04 8:02 ` Michael Straube
2022-04-04 10:50 ` Dan Carpenter
2022-04-04 11:25 ` Fabio M. De Francesco
2022-04-04 12:03 ` Dan Carpenter
2022-04-04 14:29 ` Fabio M. De Francesco
2022-04-04 14:35 ` Dan Carpenter
2022-04-04 14:47 ` Fabio M. De Francesco
2022-04-04 14:36 ` Greg KH
2022-04-04 16:33 ` Pavel Skripkin [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=c14c23a0-6b0b-04b3-e58d-786c77726874@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=sandsch@northvilleschools.net \
/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®