From: Greg KH <gregkh@linuxfoundation.org>
To: "yukuai (C)" <yukuai3@huawei.com>
Cc: laforge@gnumonks.org, arnd@arndb.de, akpm@osdl.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH] char: pcmcia: fix possible array index out of bounds in set_protocol()
Date: Fri, 21 May 2021 13:42:49 +0200 [thread overview]
Message-ID: <YKecuUjrQRAmBnss@kroah.com> (raw)
In-Reply-To: <23af0838-07c3-7113-4229-28cc82b07527@huawei.com>
On Fri, May 21, 2021 at 07:34:52PM +0800, yukuai (C) wrote:
> On 2021/05/21 18:59, Greg KH wrote:
> > On Fri, May 21, 2021 at 06:07:05PM +0800, Yu Kuai wrote:
> > > The length of array 'pts_reply' is 4, and the loop in set_protocol()
> > > will access array element from 0 to num_bytes_read - 1. Thus if
> > > io_read_num_rec_bytes() gets 'num_bytes_read' more than 4, it will
> > > cause index out of bounds errors.
> >
> > And how can num_bytes_read be greater than 4?
>
> Hi
>
> Do you mean num_bytes_read here should never be greater than 4?
>
> 544 io_read_num_rec_bytes(iobase, &num_bytes_read);
> 545 if (num_bytes_read >= 4) {
> 546 DEBUGP(2, dev, "NumRecBytes = %i\n",
> num_bytes_read);
> 547 break;
Like I said, it is tested if it is bigger, but then nothing happens if
that is true. So try to error out here.
> > Ah, it is tested, but you might want to error out if that happens, as
> > obviously something went wrong.
> >
> > Do you have this hardware to test these changes?
>
> Sorry we don't have this hardware...
Ah, then I wouldn't worry about it, as odds are, no one else does either :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-21 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 10:07 Yu Kuai
2021-05-21 10:59 ` Greg KH
2021-05-21 11:34 ` yukuai (C)
2021-05-21 11:42 ` Greg KH [this message]
2021-05-21 12:06 ` [PATCH V2] char: pcmcia: error out if 'num_bytes_read' is greater than 4 " Yu Kuai
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=YKecuUjrQRAmBnss@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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®