From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Muhammad Bilal <meatuni001@gmail.com>
Cc: "Jorge Lopez" <jorge.lopez2@hp.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v6] platform/x86: hp-bioscfg: fix heap OOB in hp_enforce_single_line_input()
Date: Wed, 21 Oct 2026 09:35:44 +0300 [thread overview]
Message-ID: <athdQF9HW4cDR7xI@ashevche-desk.local> (raw)
In-Reply-To: <20261016025352.230535-1-meatuni001@gmail.com>
On Fri, Oct 16, 2026 at 07:53:52AM +0500, Muhammad Bilal wrote:
> The input is copied with kstrdup(), which stops at the first NUL, but
> the full write size is passed to hp_enforce_single_line_input(). With
> an embedded NUL the helper reads, and can write one byte, past the
> copy. Return -EINVAL if the input contains a NUL.
>
> Tested on HP EliteBook 840 G2 (Fedora 44, Linux 7.2.8): writing "A\0"
> followed by 4093 bytes of "B" to current_password 100 times returns
> -EINVAL every time, without reading into the heap.
...
> {
> char *p;
>
> + /* buf is a string, so a NUL before count is invalid input */
> + if (strnlen(buf, count) < count)
> + return -EINVAL;
> +
> p = memchr(buf, '\n', count);
>
> if (p == buf + count - 1)
Let's look at the full implementation
int hp_enforce_single_line_input(char *buf, size_t count)
{
char *p;
p = memchr(buf, '\n', count);
if (p == buf + count - 1)
*p = '\0'; /* strip trailing newline */
else if (p)
return -EINVAL; /* enforce single line input */
return 0;
}
With your enforcement in place the rest can be simplified and refactored.
The hint is to use strnchrnul().
int hp_enforce_single_line_input(char *buf, size_t count)
{
char *p;
p = strnchrnul(buf, count, '\n');
if (p == buf + count - 1)
*p = '\0'; /* strip trailing newline */
else if (p < buf + count - 1)
return -EINVAL; /* enforce single line input */
return 0;
}
(the above done with the less intrusive changes)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-21 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 2:53 Muhammad Bilal
2026-10-20 21:19 ` Ilpo Järvinen
2026-10-21 3:41 ` Muhammad Bilal
2026-10-21 9:05 ` Ilpo Järvinen
2026-10-21 9:40 ` Ilpo Järvinen
2026-10-21 6:35 ` Andy Shevchenko [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=athdQF9HW4cDR7xI@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=meatuni001@gmail.com \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®