From: Muhammad Bilal <meatuni001@gmail.com>
To: "Jorge Lopez" <jorge.lopez2@hp.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Muhammad Bilal" <meatuni001@gmail.com>
Subject: [PATCH v4 5/9] platform/x86: hp-bioscfg: fix off-by-one in password length check
Date: Sat, 3 Oct 2026 00:14:30 +0500 [thread overview]
Message-ID: <20261002191434.58529-6-meatuni001@gmail.com> (raw)
In-Reply-To: <20261002191434.58529-1-meatuni001@gmail.com>
current_password and new_password hold MAX_PASSWD_SIZE bytes including
the NUL, but validate_password_input() accepts a password of exactly
MAX_PASSWD_SIZE characters when the firmware limits allow it.
strscpy() then truncates it and fails with -E2BIG, which
store_password_instance() ignores, so the write reports success with a
truncated password stored.
For example, with a max_password_length of 64 or more, writing 64
characters succeeds but only 63 are stored.
Reject lengths of MAX_PASSWD_SIZE or more.
Compile tested only.
Fixes: 8646a3b5ee3a ("platform/x86: hp-bioscfg: passwdobj-attributes")
Signed-off-by: Muhammad Bilal <meatuni001@gmail.com>
---
Changes in v4:
- New patch
drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c b/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
index f0551b455..a2f50ecbe 100644
--- a/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
+++ b/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
@@ -74,7 +74,7 @@ static int validate_password_input(int instance_id, const char *buf,
if (is_current && !length)
return 0;
- if (length > MAX_PASSWD_SIZE)
+ if (length >= MAX_PASSWD_SIZE)
return -E2BIG;
if (password_data->min_password_length > length ||
--
2.43.0
next prev parent reply other threads:[~2026-10-02 19:15 UTC|newest]
Thread overview: 10+ 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-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-02 19:14 ` Muhammad Bilal [this message]
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-02 19:14 ` [PATCH v4 7/9] platform/x86: hp-bioscfg: validate SPM state returned by firmware Muhammad Bilal
2026-10-02 19:14 ` [PATCH v4 8/9] platform/x86: hp-bioscfg: NUL-terminate the SPM auth token Muhammad Bilal
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=20261002191434.58529-6-meatuni001@gmail.com \
--to=meatuni001@gmail.com \
--cc=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=platform-driver-x86@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®