From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Mark Pearson <mpearson-lenovo@squebb.ca>,
"Derek J. Clark" <derekjohn.clark@gmail.com>,
Hans de Goede <hansg@kernel.org>,
stable@vger.kernel.org, Mark Pearson <markpearson@lenovo.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86: think-lmi: Fix current password length check
Date: Tue, 18 Aug 2026 16:20:10 +0300 (EEST) [thread overview]
Message-ID: <dddaae9d-88d4-bf7b-3bc1-76cd115742c2@linux.intel.com> (raw)
In-Reply-To: <aoRa_PwLxneo9Juv@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 3232 bytes --]
On Tue, 18 Aug 2026, Thorsten Blum wrote:
> On Tue, Aug 18, 2026 at 02:28:50PM +0300, Ilpo Järvinen wrote:
> > On Thu, 13 Aug 2026, Thorsten Blum wrote:
> > > current_password_store() checks the password length before removing the
> > > trailing newline, which can reject valid passwords that are exactly
> > > ->maxlen bytes long.
> > >
> > > It also passes ->maxlen to strscpy(), which truncates passwords without
> > > a newline.
> > >
> > > Use strchrnul() to measure the password length up to the newline, then
> > > copy that many bytes and add a trailing NUL terminator.
> > >
> > > Fixes: a40cd7ef22fb ("platform/x86: think-lmi: Add WMI interface support on Lenovo platforms")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> > > ---
> > > Changes in v2:
> > > - Keep and reword the newline comment
> > > - v1: https://lore.kernel.org/r/20260810132018.156868-3-thorsten.blum@linux.dev/
> > > ---
> > > drivers/platform/x86/lenovo/think-lmi.c | 8 ++++----
> > > 1 file changed, 4 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/drivers/platform/x86/lenovo/think-lmi.c b/drivers/platform/x86/lenovo/think-lmi.c
> > > index e215e86e3db7..d0ceb6aaa69e 100644
> > > --- a/drivers/platform/x86/lenovo/think-lmi.c
> > > +++ b/drivers/platform/x86/lenovo/think-lmi.c
> > > @@ -438,14 +438,14 @@ static ssize_t current_password_store(struct kobject *kobj,
> > > struct tlmi_pwd_setting *setting = to_tlmi_pwd_setting(kobj);
> > > size_t pwdlen;
> > >
> > > - pwdlen = strlen(buf);
> > > + /* Strip newline; setting password won't work if one is present. */
> > > + pwdlen = strchrnul(buf, '\n') - buf;
> > > /* pwdlen == 0 is allowed to clear the password */
> > > if (pwdlen && ((pwdlen < setting->minlen) || (pwdlen > setting->maxlen)))
> > > return -EINVAL;
> > >
> > > - strscpy(setting->password, buf, setting->maxlen);
> > > - /* Strip out CR if one is present, setting password won't work if it is present */
> > > - strreplace(setting->password, '\n', '\0');
> > > + memcpy(setting->password, buf, pwdlen);
> > > + setting->password[pwdlen] = '\0';
> >
> > Hi,
> >
> > I don't understand why is this strscpy() -> memcpy() conversion required?
>
> It's not required, strscpy() would also work.
>
> > Wouldn't it work with:
> >
> > strscpy(..., pwdlen);
> >
> > ?
>
> However, strscpy(setting->password, buf, pwdlen) wouldn't work because
> pwdlen is the number of characters to copy, but the destination buffer
> size also needs to include room for the NUL terminator. Since there is
> no NUL before pwdlen, it would copy only pwdlen - 1 characters and set
> setting->password[pwdlen - 1] = '\0'.
Okay, I was thinking in my mind if I've a off-by-one error in my
suggestion but didn't want to spend too much time on figuring it out.
> strscpy(setting->password, buf, pwdlen + 1) would work, but since we
> already know that exactly pwdlen bytes need to be copied, memcpy() is
> sufficient.
It may work, but since you then go to nul terminate it yourself, I think
using the existing function is way better than memcpy() + custom nul
termination code.
--
i.
next prev parent reply other threads:[~2026-08-18 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 8:20 [PATCH v2] platform/x86: think-lmi: Fix current password length check Thorsten Blum
2026-08-13 13:52 ` Mark Pearson
2026-08-18 11:28 ` Ilpo Järvinen
2026-08-18 13:15 ` Thorsten Blum
2026-08-18 13:20 ` Ilpo Järvinen [this message]
2026-08-18 13:39 ` Thorsten Blum
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=dddaae9d-88d4-bf7b-3bc1-76cd115742c2@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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