From: Greg KH <gregkh@linuxfoundation.org>
To: Shreenidhi Shedi <yesshedi@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Shreenidhi Shedi <sshedi@vmware.com>
Subject: Re: [PATCH 1/2] char: lp: ensure that index has not exceeded LP_NO
Date: Fri, 10 Jun 2022 15:28:04 +0200 [thread overview]
Message-ID: <YqNG5H+JbNJMeOWq@kroah.com> (raw)
In-Reply-To: <20220603130040.601673-1-sshedi@vmware.com>
On Fri, Jun 03, 2022 at 06:30:39PM +0530, Shreenidhi Shedi wrote:
> From: Shreenidhi Shedi <sshedi@vmware.com>
>
> After finishing the loop, index value can be equal to LP_NO and lp_table
> array is of size LP_NO, so this can end up in accessing an out of bound
> address in lp_register function.
>
> Signed-off-by: Shreenidhi Shedi <sshedi@vmware.com>
> ---
> drivers/char/lp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/lp.c b/drivers/char/lp.c
> index 0e22e3b0a..d474d02b6 100644
> --- a/drivers/char/lp.c
> +++ b/drivers/char/lp.c
> @@ -972,7 +972,7 @@ static void lp_attach(struct parport *port)
> if (port_num[i] == -1)
> break;
>
> - if (!lp_register(i, port))
> + if (i < LP_NO && !lp_register(i, port))
> lp_count++;
How can this ever be needed? Look at the check further up for the check
of lp_count which prevents this from every going too large.
So how can an address be accessed out of bound here?
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-10 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 13:00 [PATCH 1/2] char: lp: ensure that index has not exceeded LP_NO Shreenidhi Shedi
2022-06-03 13:00 ` [PATCH 2/2] char: lp: remove redundant initialization of err Shreenidhi Shedi
2022-06-10 13:28 ` Greg KH [this message]
2022-06-10 13:42 ` [PATCH 1/2] char: lp: ensure that index has not exceeded LP_NO Shreenidhi Shedi
2022-06-10 14:30 ` Greg KH
2022-06-11 5:45 ` Shreenidhi Shedi
2022-06-27 14:04 ` Greg KH
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=YqNG5H+JbNJMeOWq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sshedi@vmware.com \
--cc=yesshedi@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