From: <Ajay.Kathat@microchip.com>
To: <oscar.carter@gmx.com>, <adham.abozaeid@microchip.com>
Cc: <gregkh@linuxfoundation.org>, <rachel.kim@atmel.com>,
<johnny.kim@atmel.com>, <chris.park@atmel.com>,
<dean.lee@atmel.com>, <linux-wireless@vger.kernel.org>,
<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: wilc1000: Increase the size of wid_list array
Date: Fri, 1 May 2020 18:26:10 +0000 [thread overview]
Message-ID: <555a8486-8a9f-44a6-3423-78981955765a@microchip.com> (raw)
In-Reply-To: <20200501170239.16917-1-oscar.carter@gmx.com>
On 01/05/20 10:32 pm, Oscar Carter wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Increase by one the size of wid_list array as index variable can reach a
> value of 5. If this happens, an out-of-bounds access is performed.
>
> Addresses-Coverity-ID: 1451981 ("Out-of-bounds access")
> Fixes: c5c77ba18ea66 ("staging: wilc1000: Add SDIO/SPI 802.11 driver")
The code changes are fine. But the correct commit for Fixes tag should be
Fixes: f5a3cb90b802d ("staging: wilc1000: add passive scan support")
Regards,
Ajay
> Signed-off-by: Oscar Carter <oscar.carter@gmx.com>
> ---
> drivers/staging/wilc1000/hif.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wilc1000/hif.c b/drivers/staging/wilc1000/hif.c
> index 6c7de2f8d3f2..128943c3be4f 100644
> --- a/drivers/staging/wilc1000/hif.c
> +++ b/drivers/staging/wilc1000/hif.c
> @@ -151,7 +151,7 @@ int wilc_scan(struct wilc_vif *vif, u8 scan_source, u8 scan_type,
> void *user_arg, struct cfg80211_scan_request *request)
> {
> int result = 0;
> - struct wid wid_list[5];
> + struct wid wid_list[6];
> u32 index = 0;
> u32 i, scan_timeout;
> u8 *buffer;
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-05-01 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:02 Oscar Carter
2020-05-01 18:26 ` Ajay.Kathat [this message]
2020-05-03 7:32 ` Oscar Carter
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=555a8486-8a9f-44a6-3423-78981955765a@microchip.com \
--to=ajay.kathat@microchip.com \
--cc=adham.abozaeid@microchip.com \
--cc=chris.park@atmel.com \
--cc=dean.lee@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oscar.carter@gmx.com \
--cc=rachel.kim@atmel.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®