linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Peter Chen <peter.chen@freescale.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers/usb/chipidea/debuc.c: avoid out of bound read
Date: Mon, 27 Apr 2015 20:25:12 +0200	[thread overview]
Message-ID: <553E7F08.7070205@gmx.de> (raw)
In-Reply-To: <20150422012633.GA2680@shlinux2>

On 22.04.2015 03:26, Peter Chen wrote:
> On Tue, Apr 21, 2015 at 09:25:41PM +0200, Heinrich Schuchardt wrote:
>> Hello Peter,
>>
>> thanks for reviewing.
>>
>> On 21.04.2015 03:32, Peter Chen wrote:
>>> On Fri, Apr 17, 2015 at 08:04:13AM +0200, Heinrich Schuchardt wrote:
>>>> A string written by the user may not be zero terminated.
>>>>
>>>> sscanf may read memory beyond the buffer if no zero byte
>>>> is found.
>>>>
>>>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>>>> ---
>>>>  drivers/usb/chipidea/debug.c | 6 +++++-
>>>>  1 file changed, 5 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/usb/chipidea/debug.c b/drivers/usb/chipidea/debug.c
>>>> index dfb05ed..ef08af3 100644
>>>> --- a/drivers/usb/chipidea/debug.c
>>>> +++ b/drivers/usb/chipidea/debug.c
>>>> @@ -88,9 +88,13 @@ static ssize_t ci_port_test_write(struct file *file, const char __user *ubuf,
>>>>  	char buf[32];
>>>>  	int ret;
>>>>  
>>>> -	if (copy_from_user(buf, ubuf, min_t(size_t, sizeof(buf) - 1, count)))
>>>> +	count = min_t(size_t, sizeof(buf) - 1, count);
>>>> +	if (copy_from_user(buf, ubuf, count))
>>>>  		return -EFAULT;
>>>
>>> Any reasons to change above?
>>
>> Otherwise we would have two lines with the term
>> min_t(size_t, sizeof(buf) - 1, count).
> 
> Sorry, two lines of min_t(..)? Why I can't find it?

Hello Peter,

in my patch I write:

count = min_t(size_t, sizeof(buf) - 1, count);
if (copy_from_user(buf, ubuf, count))
	return -EFAULT;

/* sscanf requires a zero terminated string */
buf[count] = 0;

Without the first part of the change I would have had to write:

if (copy_from_user(buf, ubuf, min_t(size_t, sizeof(buf) - 1, count)))
	return -EFAULT;

/* sscanf requires a zero terminated string */
buf[min_t(size_t, sizeof(buf) - 1, count)] = 0;

We should do the same calculation
"min_t(size_t, sizeof(buf) - 1, count)"
only once in the coding.

Best regards

Heinrich


> 
> 
>>
>> This would make the code harder to read.
>>
>>>>  
>>>> +	/* sscanf requires a zero terminated string */
>>>> +	buf[count] = 0;
>>>> +
>>>
>>> I prefer using '\0'
>>
>> If you confirm the rest of the patch is ok, I will send an updated patch.
>>
>> Best regards
>>
>> Heinrich
>>
>>>
>>>>  	if (sscanf(buf, "%u", &mode) != 1)
>>>>  		return -EINVAL;
>>>>  
>>
> 


  reply	other threads:[~2015-04-27 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  6:04 [PATCH 1/1] drivers/usb/chipidea/debuc.c: avoid out of bound read Heinrich Schuchardt
2015-04-21  1:32 ` Peter Chen
2015-04-21 19:25   ` Heinrich Schuchardt
2015-04-22  1:26     ` Peter Chen
2015-04-27 18:25       ` Heinrich Schuchardt [this message]
2015-04-28  8:22         ` Peter Chen
2015-04-28 17:30           ` [PATCH 1/1 v2] " Heinrich Schuchardt

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=553E7F08.7070205@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@freescale.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;
as well as URLs for NNTP newsgroup(s).