From: Kees Cook <keescook@chromium.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] hostap: Add __counted_by for struct prism2_download_data and use struct_size()
Date: Mon, 9 Oct 2023 12:54:28 -0700 [thread overview]
Message-ID: <202310091253.665A9C9@keescook> (raw)
In-Reply-To: <ZSRXXvWMMkm7qqRW@work>
On Mon, Oct 09, 2023 at 01:41:18PM -0600, Gustavo A. R. Silva wrote:
> Prepare for the coming implementation by GCC and Clang of the __counted_by
> attribute. Flexible array members annotated with __counted_by can have
> their accesses bounds-checked at run-time via CONFIG_UBSAN_BOUNDS (for
> array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family
> functions).
>
> While there, use struct_size() helper, instead of the open-coded
> version, to calculate the size for the allocation of the whole
> flexible structure, including of course, the flexible-array member.
>
> This code was found with the help of Coccinelle, and audited and
> fixed manually.
>
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> ---
> drivers/net/wireless/intersil/hostap/hostap_download.c | 3 +--
> drivers/net/wireless/intersil/hostap/hostap_wlan.h | 2 +-
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/intersil/hostap/hostap_download.c b/drivers/net/wireless/intersil/hostap/hostap_download.c
> index 3672291ced5c..5e5bada28b5b 100644
> --- a/drivers/net/wireless/intersil/hostap/hostap_download.c
> +++ b/drivers/net/wireless/intersil/hostap/hostap_download.c
> @@ -732,8 +732,7 @@ static int prism2_download(local_info_t *local,
> goto out;
> }
>
> - dl = kzalloc(sizeof(*dl) + param->num_areas *
> - sizeof(struct prism2_download_data_area), GFP_KERNEL);
> + dl = kzalloc(struct_size(dl, data, param->num_areas), GFP_KERNEL);
> if (dl == NULL) {
> ret = -ENOMEM;
> goto out;
> diff --git a/drivers/net/wireless/intersil/hostap/hostap_wlan.h b/drivers/net/wireless/intersil/hostap/hostap_wlan.h
> index c25cd21d18bd..f71c0545c0be 100644
> --- a/drivers/net/wireless/intersil/hostap/hostap_wlan.h
> +++ b/drivers/net/wireless/intersil/hostap/hostap_wlan.h
> @@ -617,7 +617,7 @@ struct prism2_download_data {
> u32 addr; /* wlan card address */
> u32 len;
> u8 *data; /* allocated data */
> - } data[];
> + } data[] __counted_by(num_areas);
> };
Should this be considered a v2 of:
https://lore.kernel.org/linux-hardening/94848cc3-6f5c-46d7-8cc7-98a4f10865b3@embeddedor.com/
?
Yours is more complete since it includes the struct_size() change...
--
Kees Cook
next prev parent reply other threads:[~2023-10-09 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 19:41 [PATCH][next] hostap: Add __counted_by for struct prism2_download_data and use struct_size() Gustavo A. R. Silva
2023-10-09 19:54 ` Kees Cook [this message]
2023-10-09 20:33 ` Gustavo A. R. Silva
2023-10-09 20:42 ` Kees Cook
2023-10-10 6:17 ` Kalle Valo
2023-10-10 12:44 ` Gustavo A. R. Silva
2023-10-10 22:50 ` Kees Cook
2023-10-10 23:24 ` Gustavo A. R. Silva
2023-10-11 9:20 ` [next] wifi: " Kalle Valo
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=202310091253.665A9C9@keescook \
--to=keescook@chromium.org \
--cc=gustavoars@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.