From: Thorsten Blum <thorsten.blum@linux.dev>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: "Derek J . Clark" <derekjohn.clark@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
stable@vger.kernel.org, "Mark Pearson" <markpearson@lenovo.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: think-lmi: Fix current password length check
Date: Tue, 11 Aug 2026 22:29:27 +0200 [thread overview]
Message-ID: <anuGJ59lNNX7YouI@linux.dev> (raw)
In-Reply-To: <15a1d7e9-f882-44ce-a24f-89b266e80efa@app.fastmail.com>
On Tue, Aug 11, 2026 at 03:29:28PM -0400, Mark Pearson wrote:
> On Mon, Aug 10, 2026, at 9:20 AM, 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>
> > ---
> > drivers/platform/x86/lenovo/think-lmi.c | 8 +++-----
> > 1 file changed, 3 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/platform/x86/lenovo/think-lmi.c
> > b/drivers/platform/x86/lenovo/think-lmi.c
> > index e215e86e3db7..860224dc8c21 100644
> > --- a/drivers/platform/x86/lenovo/think-lmi.c
> > +++ b/drivers/platform/x86/lenovo/think-lmi.c
> > @@ -436,16 +436,14 @@ static ssize_t current_password_store(struct
> > kobject *kobj,
> > const char *buf, size_t count)
> > {
> > struct tlmi_pwd_setting *setting = to_tlmi_pwd_setting(kobj);
> > - size_t pwdlen;
> > + size_t pwdlen = strchrnul(buf, '\n') - buf;
> >
> > - pwdlen = strlen(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';
> > return count;
> > }
>
> Change is good.
> Only minor note is that I hate to lose the comment explaining why
> we're losing the CR. Can we put that back in above the strchrnul
> operation?
I removed the comment because '\r' is CR and '\n' is LF. Happy to add it
back if needed, but maybe a better version would be:
/* Strip newline; setting password won't work if one is present. */
next prev parent reply other threads:[~2026-08-11 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 13:20 [PATCH] platform/x86: think-lmi: Fix current password length check Thorsten Blum
2026-08-11 19:29 ` Mark Pearson
2026-08-11 20:29 ` Thorsten Blum [this message]
2026-08-12 0:18 ` Mark Pearson
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=anuGJ59lNNX7YouI@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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 \
/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.