mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Muhammad Bilal <meatuni001@gmail.com>
Cc: "Jorge Lopez" <jorge.lopez2@hp.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	platform-driver-x86@vger.kernel.org,
	LKML <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 12:05:40 +0300 (EEST)	[thread overview]
Message-ID: <a905f45d-aec8-569f-d5bc-718896f7c9c9@linux.intel.com> (raw)
In-Reply-To: <CADqcGBkV4iE_0j6usv6TvV3K9XGUa0L9J-ebUkTLsB0NBYzTHA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]

On Wed, 21 Oct 2026, Muhammad Bilal wrote:

> Hi Ilpo,
> 
> > Why use n variant?
> strnlen() keeps the read within count, which is the size of buf as far
> as this helper knows, so it does not depend on the caller NUL
> terminating the buffer. Both current callers pass a kstrdup() copy, so
> strlen() works too. I can switch to it in v7 if you prefer.

As the contract here is the input must be a string, I don't see any need 
to limit the length with n variant so I do prefer strlen(). Also, we know 
that it should not be longer than count anyway.

--
 i.

> Thanks
> Muhammad
> 
> On Wed, Oct 21, 2026 at 2:19 AM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > On Fri, 16 Oct 2026, 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.
> > >
> > > Fixes: a34fc329b189 ("platform/x86: hp-bioscfg: bioscfg")
> > > Cc: stable@vger.kernel.org
> > > Suggested-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > Signed-off-by: Muhammad Bilal <meatuni001@gmail.com>
> > > ---
> > > Changes in v6:
> > >  - Return -EINVAL on embedded NUL instead of limiting the scan (Ilpo)
> > >
> > > v5: https://lore.kernel.org/all/20261007134711.473857-1-meatuni001@gmail.com/
> > >
> > >  drivers/platform/x86/hp/hp-bioscfg/bioscfg.c | 4 ++++
> > >  1 file changed, 4 insertions(+)
> > >
> > > diff --git a/drivers/platform/x86/hp/hp-bioscfg/bioscfg.c b/drivers/platform/x86/hp/hp-bioscfg/bioscfg.c
> > > index 876fc35d035b..e306bd8b1e72 100644
> > > --- a/drivers/platform/x86/hp/hp-bioscfg/bioscfg.c
> > > +++ b/drivers/platform/x86/hp/hp-bioscfg/bioscfg.c
> > > @@ -162,6 +162,10 @@ int hp_enforce_single_line_input(char *buf, size_t count)
> > >  {
> > >       char *p;
> > >
> > > +     /* buf is a string, so a NUL before count is invalid input */
> > > +     if (strnlen(buf, count) < count)
> >
> > Why use n variant?
> >
> > > +             return -EINVAL;
> > > +
> > >       p = memchr(buf, '\n', count);
> > >
> > >       if (p == buf + count - 1)
> > >
> > > base-commit: 8667bd30fd033295b3038ce374c551d1059538ba
> > >
> >
> > --
> >  i.
> 

  reply	other threads:[~2026-10-21  9:05 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 [this message]
2026-10-21  9:40       ` Ilpo Järvinen
2026-10-21  6:35 ` Andy Shevchenko

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=a905f45d-aec8-569f-d5bc-718896f7c9c9@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hansg@kernel.org \
    --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®