From: Kees Cook <keescook@chromium.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: "Gustavo A . R . Silva" <gustavoars@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 05/32] brcmfmac: Use mem_to_flex_dup() with struct brcmf_fweh_queue_item
Date: Mon, 16 May 2022 20:57:42 -0700 [thread overview]
Message-ID: <202205162056.F8D1BF3E@keescook> (raw)
In-Reply-To: <b197ca6d-4285-5310-7e98-918c885a2e38@broadcom.com>
On Mon, May 16, 2022 at 02:49:21PM +0200, Arend van Spriel wrote:
> On 5/4/2022 3:44 AM, Kees Cook wrote:
> > As part of the work to perform bounds checking on all memcpy() uses,
> > replace the open-coded a deserialization of bytes out of memory into a
> > trailing flexible array by using a flex_array.h helper to perform the
> > allocation, bounds checking, and copying.
> >
> Reviewed-by: Arend van Spriel <aspriel@gmail.com>
Thanks!
> > [...]
> > diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c
> > index bc3f4e4edcdf..bea798ca6466 100644
> > --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c
> > +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c
> > @@ -32,8 +32,8 @@ struct brcmf_fweh_queue_item {
> > u8 ifidx;
> > u8 ifaddr[ETH_ALEN];
> > struct brcmf_event_msg_be emsg;
> > - u32 datalen;
> > - u8 data[];
> > + DECLARE_FLEX_ARRAY_ELEMENTS_COUNT(u32, datalen);
> > + DECLARE_FLEX_ARRAY_ELEMENTS(u8, data);
> > };
> > [...]
> > @@ -414,8 +414,7 @@ void brcmf_fweh_process_event(struct brcmf_pub *drvr,
> > datalen + sizeof(*event_packet) > packet_len)
> > return;
> > - event = kzalloc(sizeof(*event) + datalen, gfp);
> > - if (!event)
> > + if (mem_to_flex_dup(&event, data, datalen, gfp))
> > return;
> > event->code = code;
> > @@ -423,8 +422,6 @@ void brcmf_fweh_process_event(struct brcmf_pub *drvr,
> > /* use memcpy to get aligned event message */
> > memcpy(&event->emsg, &event_packet->msg, sizeof(event->emsg));
> > - memcpy(event->data, data, datalen);
> > - event->datalen = datalen;
>
> So does mem_to_flex_dup() store event->datalen?
>
> Don't have the entire thread so missing bits and pieces, but at least this
> raises questions for me.
Yes, that's part of the internal workings here -- the flex array counter
is declared and will be set as part of the copy.
--
Kees Cook
prev parent reply other threads:[~2022-05-17 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220504014440.3697851-1-keescook@chromium.org>
[not found] ` <20220504014440.3697851-6-keescook@chromium.org>
2022-05-16 12:49 ` [PATCH 05/32] brcmfmac: Use mem_to_flex_dup() with struct brcmf_fweh_queue_item Arend van Spriel
2022-05-17 3:57 ` Kees Cook [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=202205162056.F8D1BF3E@keescook \
--to=keescook@chromium.org \
--cc=arend.vanspriel@broadcom.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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