From: Yasuaki Torimaru <yasuakitorimaru@gmail.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ajay.kathat@microchip.com,
claudiu.beznea@tuxon.dev, kees@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation
Date: Wed, 25 Mar 2026 00:07:07 +0900 [thread overview]
Message-ID: <CAA2s7u7jpm2Q=18+pAxC2szqUjQ+3xSXokCT85YsAFKOLf4Zsw@mail.gmail.com> (raw)
In-Reply-To: <accee45c-7cae-48fc-b868-b7404b8c061c@oss.qualcomm.com>
On Tue, 25 Mar 2026, Jeff Johnson wrote:
> Reviewed-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
>
> Another thing to note is it is very strange that the struct wid that defines
> the TLV format uses a signed type for both the TLV length and
payload pointer:
> s32 size;
> s8 *val;
>
> I don't think I've ever seen this in a TLV representation!
Thank you for the review.
Good point — signed types for TLV length and payload are indeed unusual
and could mask subtle sign-extension bugs. I'll look into a follow-up
cleanup patch for struct wid once this fix lands.
Thanks,
Yasuaki
2026年3月24日(火) 23:50 Jeff Johnson <jeff.johnson@oss.qualcomm.com>:
>
> On 3/24/2026 3:06 AM, Yasuaki Torimaru wrote:
> > The variable valuesize is declared as u8 but accumulates the total
> > length of all SSIDs to scan. Each SSID contributes up to 33 bytes
> > (IEEE80211_MAX_SSID_LEN + 1), and with WILC_MAX_NUM_PROBED_SSID (10)
> > SSIDs the total can reach 330, which wraps around to 74 when stored
> > in a u8.
> >
> > This causes kmalloc to allocate only 75 bytes while the subsequent
> > memcpy writes up to 331 bytes into the buffer, resulting in a 256-byte
> > heap buffer overflow.
> >
> > Widen valuesize from u8 to u32 to accommodate the full range.
> >
> > Fixes: c5c77ba18ea6 ("staging: wilc1000: Add SDIO/SPI 802.11 driver")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Yasuaki Torimaru <yasuakitorimaru@gmail.com>
>
> Reviewed-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
>
> Another thing to note is it is very strange that the struct wid that defines
> the TLV format uses a signed type for both the TLV length and payload pointer:
> s32 size;
> s8 *val;
>
> I don't think I've ever seen this in a TLV representation!
>
> > ---
> > drivers/net/wireless/microchip/wilc1000/hif.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/microchip/wilc1000/hif.c b/drivers/net/wireless/microchip/wilc1000/hif.c
> > index f354b11cb919..944b2a812b63 100644
> > --- a/drivers/net/wireless/microchip/wilc1000/hif.c
> > +++ b/drivers/net/wireless/microchip/wilc1000/hif.c
> > @@ -163,7 +163,7 @@ int wilc_scan(struct wilc_vif *vif, u8 scan_source,
> > u32 index = 0;
> > u32 i, scan_timeout;
> > u8 *buffer;
> > - u8 valuesize = 0;
> > + u32 valuesize = 0;
> > u8 *search_ssid_vals = NULL;
> > const u8 ch_list_len = request->n_channels;
> > struct host_if_drv *hif_drv = vif->hif_drv;
>
prev parent reply other threads:[~2026-03-24 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 10:06 [PATCH] wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation Yasuaki Torimaru
2026-03-24 14:49 ` Jeff Johnson
2026-03-24 15:07 ` Yasuaki Torimaru [this message]
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='CAA2s7u7jpm2Q=18+pAxC2szqUjQ+3xSXokCT85YsAFKOLf4Zsw@mail.gmail.com' \
--to=yasuakitorimaru@gmail.com \
--cc=ajay.kathat@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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