From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 2/9] scan: fix out of bound array access for survey results
Date: Wed, 16 Apr 2025 10:21:10 -0700 [thread overview]
Message-ID: <667e6c01-9782-4bf9-a2ed-971783c896f7@gmail.com> (raw)
In-Reply-To: <b527f1e2-a619-45e9-b551-50482ba26588@gmail.com>
On 4/16/25 10:20 AM, Denis Kenzior wrote:
> Hi James,
>
> On 4/16/25 7:34 AM, James Prestwood wrote:
>> The survey arrays were exactly the number of valid channels for a
>> given band (e.g. 14 for 2.4GHz) but since channels start at 1 this
>> means that the last channel for a band would overflow the array.
>> ---
>> src/scan.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>
> Can I get some Fixes: tags for these?
Sure, I'll see what I can gather up.
>
> Regards,
> -Denis
next prev parent reply other threads:[~2025-04-16 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:34 [PATCH 1/9] monitor: fix spelling Exausted -> Exhausted James Prestwood
2025-04-16 12:34 ` [PATCH 2/9] scan: fix out of bound array access for survey results James Prestwood
2025-04-16 17:20 ` Denis Kenzior
2025-04-16 17:21 ` James Prestwood [this message]
2025-04-16 12:34 ` [PATCH 3/9] dpp-util: fail on duplicate values in URI James Prestwood
2025-04-16 12:34 ` [PATCH 4/9] unit: add test for duplicate URI elements James Prestwood
2025-04-16 12:34 ` [PATCH 5/9] monitor: add size check for interworking IE parsing James Prestwood
2025-04-16 12:34 ` [PATCH 6/9] storage: add length check in __storage_decrypt James Prestwood
2025-04-16 12:34 ` [PATCH 7/9] unit: add test-storage James Prestwood
2025-04-16 12:34 ` [PATCH 8/9] station: check return when advancing iterator James Prestwood
2025-04-16 12:34 ` [PATCH 9/9] eap-mschapv2: Fix leak of state->user on error path James Prestwood
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=667e6c01-9782-4bf9-a2ed-971783c896f7@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
/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