From: Muhammad Bilal <meatuni001@gmail.com>
To: jorge.lopez2@hp.com, hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: andy.shevchenko@gmail.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Muhammad Bilal <meatuni001@gmail.com>
Subject: [PATCH v3 0/3] platform/x86: hp-bioscfg: string buffer and password fixes
Date: Wed, 30 Sep 2026 23:30:15 +0500 [thread overview]
Message-ID: <20260930183018.49629-1-meatuni001@gmail.com> (raw)
Fix string parsing in hp_get_string_from_buffer() and make over-length
password writes fail.
Changes in v3:
- Drop Suggested-by: Andy Shevchenko from patch 2, tidy its includes
and declarations (Andy)
- Return -E2BIG instead of -ERANGE in patch 3 (Andy)
- Drop a blank line in the declarations in patch 1 (Andy)
Changes in v2:
- Split the hp_get_string_from_buffer() fix in two (Ilpo)
- Drop the lib/string_helpers patch, use @only of string_escape_mem()
instead (Andy)
- Add patch 3
Muhammad Bilal (3):
platform/x86: hp-bioscfg: fix OOB reads in hp_get_string_from_buffer()
platform/x86: hp-bioscfg: fix non-ASCII truncation in
hp_get_string_from_buffer()
platform/x86: hp-bioscfg: return -E2BIG from validate_password_input()
drivers/platform/x86/hp/hp-bioscfg/bioscfg.c | 79 ++++++-------------
.../x86/hp/hp-bioscfg/passwdobj-attributes.c | 7 +-
2 files changed, 28 insertions(+), 58 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-30 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 18:30 Muhammad Bilal [this message]
2026-09-30 18:30 ` [PATCH v3 1/3] platform/x86: hp-bioscfg: fix OOB reads in hp_get_string_from_buffer() Muhammad Bilal
2026-09-30 18:30 ` [PATCH v3 2/3] platform/x86: hp-bioscfg: fix non-ASCII truncation " Muhammad Bilal
2026-09-30 18:30 ` [PATCH v3 3/3] platform/x86: hp-bioscfg: return -E2BIG from validate_password_input() Muhammad Bilal
2026-09-30 18:38 ` [PATCH v3 0/3] platform/x86: hp-bioscfg: string buffer and password fixes 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=20260930183018.49629-1-meatuni001@gmail.com \
--to=meatuni001@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.