mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v4 1/9] platform/x86: hp-bioscfg: fix OOB reads in hp_get_string_from_buffer()
Date: Sat, 3 Oct 2026 23:14:51 +0300	[thread overview]
Message-ID: <asFiO0hjqzGdmAMn@ashevche-desk.local> (raw)
In-Reply-To: <20261002191434.58529-2-meatuni001@gmail.com>

On Sat, Oct 03, 2026 at 12:14:26AM +0500, Muhammad Bilal wrote:
> The escape prescan loop uses 'size' as both its bound and its
> accumulator, so each escape character found extends the loop and
> reads past the end of src[].
> 
> Use the original u16 count as the loop bound. Also include the 2-byte
> length prefix in the bounds check, pass the u16 count instead of the
> byte count to utf16s_to_utf8s(), and advance the buffer by the bytes
> actually consumed instead of the escape-inflated count.
> 
> Tested on HP EliteBook 840 G2 (Fedora 44, Linux 7.2.7).

...

> -	/* Ensure there is enough space remaining to read and convert
> -	 * the string
> +	/* Ensure there is enough space remaining for the length prefix
> +	 * just read plus the string data it describes.
>  	 */

/*
 * While at it, fix the comment style for
 * multi-line comments. You can use this example.
 */

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-10-03 20:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 19:14 [PATCH v4 0/9] platform/x86: hp-bioscfg: buffer handling fixes Muhammad Bilal
2026-10-02 19:14 ` [PATCH v4 1/9] platform/x86: hp-bioscfg: fix OOB reads in hp_get_string_from_buffer() Muhammad Bilal
2026-10-03 20:14   ` Andy Shevchenko [this message]
2026-10-02 19:14 ` [PATCH v4 2/9] platform/x86: hp-bioscfg: fix non-ASCII truncation " Muhammad Bilal
2026-10-02 19:14 ` [PATCH v4 3/9] platform/x86: hp-bioscfg: return -E2BIG from validate_password_input() Muhammad Bilal
2026-10-02 19:14 ` [PATCH v4 4/9] platform/x86: hp-bioscfg: allow clearing current_password Muhammad Bilal
2026-10-05 13:13   ` Ilpo Järvinen
2026-10-02 19:14 ` [PATCH v4 5/9] platform/x86: hp-bioscfg: fix off-by-one in password length check Muhammad Bilal
2026-10-02 19:14 ` [PATCH v4 6/9] platform/x86: hp-bioscfg: fix heap OOB with embedded NUL in store paths Muhammad Bilal
2026-10-05 13:25   ` Ilpo Järvinen
2026-10-02 19:14 ` [PATCH v4 7/9] platform/x86: hp-bioscfg: validate SPM state returned by firmware Muhammad Bilal
2026-10-05 13:28   ` Ilpo Järvinen
2026-10-02 19:14 ` [PATCH v4 8/9] platform/x86: hp-bioscfg: NUL-terminate the SPM auth token Muhammad Bilal
2026-10-05 13:41   ` Ilpo Järvinen
2026-10-02 19:14 ` [PATCH v4 9/9] platform/x86: hp-bioscfg: fix oops on short integer attribute buffer Muhammad Bilal

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=asFiO0hjqzGdmAMn@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®