From: Kees Cook <keescook@chromium.org>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Kalle Valo <kvalo@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-wireless@vger.kernel.org, linux-hardening@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] wifi: p54: Annotate struct p54_cal_database with __counted_by
Date: Mon, 9 Oct 2023 09:18:52 -0700 [thread overview]
Message-ID: <202310090914.A6BAAB9@keescook> (raw)
In-Reply-To: <CAKf6xptEEHJAsrwh_oebK1_AMb+_tvLtiY8sP-Qk=Z9jXhVf7Q@mail.gmail.com>
On Mon, Oct 09, 2023 at 10:55:32AM -0400, Jason Andryuk wrote:
> This is the function that creates struct p54_cal_database:
>
> static struct p54_cal_database *p54_convert_db(struct pda_custom_wrapper *src,
> size_t total_len)
> {
> struct p54_cal_database *dst;
> size_t payload_len, entries, entry_size, offset;
>
> payload_len = le16_to_cpu(src->len);
> entries = le16_to_cpu(src->entries);
> entry_size = le16_to_cpu(src->entry_size);
> offset = le16_to_cpu(src->offset);
> if (((entries * entry_size + offset) != payload_len) ||
> (payload_len + sizeof(*src) != total_len))
> return NULL;
>
> dst = kmalloc(sizeof(*dst) + payload_len, GFP_KERNEL);
> if (!dst)
> return NULL;
>
> dst->entries = entries;
> dst->entry_size = entry_size;
> dst->offset = offset;
> dst->len = payload_len;
>
> memcpy(dst->data, src->data, payload_len);
> return dst;
> }
>
> You can see that kmalloc is performed with `sizeof(*dst) +
> payload_len`, and payload_len is assigned to ->len.
>
> I don't read Coccinelle, but, if this patch was auto-generated, I
> wonder if the script has an error.
It seems that my Coccinelle script got confused by this:
p54_convert_output_limits():
priv->output_limit = kmalloc(data[1] *
sizeof(struct pda_channel_output_limit) +
sizeof(*priv->output_limit), GFP_KERNEL);
...
priv->output_limit->entry_size =
sizeof(struct pda_channel_output_limit);
priv->output_limit->len = priv->output_limit->entry_size *
priv->output_limit->entries +
priv->output_limit->offset;
It thought "sizeof(struct pda_channel_output_limit)" was the element
count, since it wasn't able to identify the array member here.
Regardless, I've sent a v2 now. :)
--
Kees Cook
prev parent reply other threads:[~2023-10-09 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 20:17 [PATCH] wifi: p54: Annotate struct p54_cal_database with __counted_by Kees Cook
2023-10-06 20:49 ` Gustavo A. R. Silva
2023-10-09 14:55 ` Jason Andryuk
2023-10-09 15:03 ` Gustavo A. R. Silva
2023-10-09 16:07 ` Kees Cook
2023-10-09 16:18 ` 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=202310090914.A6BAAB9@keescook \
--to=keescook@chromium.org \
--cc=chunkeey@googlemail.com \
--cc=gustavoars@kernel.org \
--cc=jandryuk@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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