From: Kees Cook <keescook@chromium.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: tony.luck@intel.com, gpiccoli@igalia.com,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pstore/platform: Add check for kstrdup
Date: Thu, 22 Jun 2023 09:15:56 -0700 [thread overview]
Message-ID: <202306220914.E881234A2C@keescook> (raw)
In-Reply-To: <20230615025312.48712-1-jiasheng@iscas.ac.cn>
On Thu, Jun 15, 2023 at 10:53:12AM +0800, Jiasheng Jiang wrote:
> Add check for the return value of kstrdup() and return the error
> if it fails in order to avoid NULL pointer dereference.
>
> Fixes: 563ca40ddf40 ("pstore/platform: Switch pstore_info::name to const")
> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Thanks, this is looking better!
> ---
> Changelog:
>
> v1 -> v2:
>
> 1. Allocate a copy earlier.
> ---
> fs/pstore/platform.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c
> index cbc0b468c1ab..727f8ce71062 100644
> --- a/fs/pstore/platform.c
> +++ b/fs/pstore/platform.c
> @@ -573,6 +573,8 @@ static int pstore_write_user_compat(struct pstore_record *record,
> */
> int pstore_register(struct pstore_info *psi)
> {
> + char *new_backend;
> +
> if (backend && strcmp(backend, psi->name)) {
> pr_warn("backend '%s' already in use: ignoring '%s'\n",
> backend, psi->name);
> @@ -593,6 +595,10 @@ int pstore_register(struct pstore_info *psi)
> return -EINVAL;
> }
>
> + new_backend = kstrdup(psi->name, GFP_KERNEL);
> + if (!new_backend)
> + return -ENOMEM;
> +
> mutex_lock(&psinfo_lock);
> if (psinfo) {
> pr_warn("backend '%s' already loaded: ignoring '%s'\n",
In my suggestion I had included a kfree() for new_backend in this above
error path, which is missing here. Can you respin it with that added?
> @@ -630,7 +636,7 @@ int pstore_register(struct pstore_info *psi)
> * Update the module parameter backend, so it is visible
> * through /sys/module/pstore/parameters/backend
> */
> - backend = kstrdup(psi->name, GFP_KERNEL);
> + backend = new_backend;
>
> pr_info("Registered %s as persistent store backend\n", psi->name);
>
> --
> 2.25.1
>
But otherwise, yeah, looks good. Thanks!
--
Kees Cook
prev parent reply other threads:[~2023-06-22 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 2:53 [PATCH v2] pstore/platform: Add check for kstrdup Jiasheng Jiang
2023-06-22 16:15 ` Kees Cook [this message]
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=202306220914.E881234A2C@keescook \
--to=keescook@chromium.org \
--cc=gpiccoli@igalia.com \
--cc=jiasheng@iscas.ac.cn \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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