From: Dan Carpenter <dan.carpenter@linaro.org>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: markus.elfring@web.de, Shyam-sundar.S-k@amd.com,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/amd/pmf: Use memdup_user()
Date: Thu, 30 May 2024 22:28:34 +0300 [thread overview]
Message-ID: <1512f46e-112c-47ef-8620-add0f04ce86d@moroto.mountain> (raw)
In-Reply-To: <1D5BDE66-ABB3-41D9-ACB0-FBAC207D55DC@toblux.com>
On Thu, May 30, 2024 at 04:15:51PM +0200, Thorsten Blum wrote:
> Hi Dan,
>
> On 27. May 2024, at 12:38, Dan Carpenter <dan.carpenter@linaro.org> wrote:
> > Also this check isn't great:
> >
> > if (dev->policy_sz < header->length + 512)
> >
> > header->length is a u32 that comes from the user, so the addition can
> > overflow. I can't immediately see how to exploit this though since we
> > don't seem to use header->length after this (by itself).
>
> How about
>
> if (header->length > U32_MAX - 512 || dev->policy_sz < header->length + 512)
> return -EINVAL;
>
> to prevent a possible overflow?
I've been thinking about this and actually we could do something simpler:
if (dev->policy_sz < size_add(header->length, 512)) {
>
> header->length is used in the next line
>
> dev->policy_sz = header->length + 512;
Yeah, but it's not used by itself. The "header->length + 512" has been
verified as a valid value whether it overflows or not. Only
"header->length" is wrong.
>
> and if the addition overflows, we end up setting dev->policy_sz to an
> invalid value.
regards,
dan carpenter
prev parent reply other threads:[~2024-05-30 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:46 [PATCH] " Thorsten Blum
2024-05-10 11:12 ` Markus Elfring
2024-05-27 8:36 ` [PATCH v2] " Thorsten Blum
2024-05-27 10:15 ` Ilpo Järvinen
2024-05-27 10:38 ` Dan Carpenter
2024-05-30 14:15 ` Thorsten Blum
2024-05-30 19:28 ` Dan Carpenter [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=1512f46e-112c-47ef-8620-add0f04ce86d@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.elfring@web.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thorsten.blum@toblux.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
all inboxes | Powered by JetHome®