From: Jolly Shah <JOLLYS@xilinx.com>
To: Jann Horn <jannh@google.com>, Michal Simek <michals@xilinx.com>
Cc: Rajan Vaja <RAJANV@xilinx.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] firmware: xilinx: fix debugfs write handler
Date: Tue, 5 Mar 2019 18:57:05 +0000 [thread overview]
Message-ID: <BYAPR02MB599297A2EB81002FA34AC401B8720@BYAPR02MB5992.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20190218214309.29985-1-jannh@google.com>
Acked-by: Jolly Shah <jollys@xilinx.com>
> -----Original Message-----
> From: Jann Horn <jannh@google.com>
> Sent: Monday, February 18, 2019 1:43 PM
> To: Michal Simek <michals@xilinx.com>; jannh@google.com
> Cc: Rajan Vaja <RAJANV@xilinx.com>; Jolly Shah <JOLLYS@xilinx.com>; linux-
> arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] firmware: xilinx: fix debugfs write handler
>
> - Userspace wants to write a string with `len` bytes, not counting the
> terminating NULL, so we should allocate `len+1` bytes. It looks like the
> current code relied on having a nullbyte directly behind `kern_buff`,
> which happens to work reliably as long as `len` isn't one of the kmalloc
> size classes.
> - strncpy_from_user() is completely wrong here; userspace is giving us a
> (not necessarily null-terminated) buffer and its length.
> strncpy_from_user() is for cases in which we don't know the length.
> - Don't let broken userspace allocate arbitrarily big kmalloc allocations.
>
> Just use memdup_user_nul(), which is designed precisely for things like
> this.
>
> Signed-off-by: Jann Horn <jannh@google.com>
> ---
> WARNING: completely untested patch
>
> drivers/firmware/xilinx/zynqmp-debug.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/firmware/xilinx/zynqmp-debug.c
> b/drivers/firmware/xilinx/zynqmp-debug.c
> index 2771df6df379..90b66cdbfd58 100644
> --- a/drivers/firmware/xilinx/zynqmp-debug.c
> +++ b/drivers/firmware/xilinx/zynqmp-debug.c
> @@ -163,21 +163,14 @@ static ssize_t zynqmp_pm_debugfs_api_write(struct
> file *file,
>
> strcpy(debugfs_buf, "");
>
> - if (*off != 0 || len == 0)
> + if (*off != 0 || len <= 1 || len > PAGE_SIZE - 1)
> return -EINVAL;
>
> - kern_buff = kzalloc(len, GFP_KERNEL);
> - if (!kern_buff)
> - return -ENOMEM;
> -
> + kern_buff = memdup_user_nul(ptr, len);
> + if (IS_ERR(kern_buff))
> + return PTR_ERR(kern_buff);
> tmp_buff = kern_buff;
>
> - ret = strncpy_from_user(kern_buff, ptr, len);
> - if (ret < 0) {
> - ret = -EFAULT;
> - goto err;
> - }
> -
> /* Read the API name from a user request */
> pm_api_req = strsep(&kern_buff, " ");
>
> --
> 2.21.0.rc0.258.g878e2cd30e-goog
next prev parent reply other threads:[~2019-03-05 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 21:43 Jann Horn
2019-02-28 13:59 ` Michal Simek
2019-03-05 18:57 ` Jolly Shah [this message]
2019-03-18 12:44 ` Michal Simek
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=BYAPR02MB599297A2EB81002FA34AC401B8720@BYAPR02MB5992.namprd02.prod.outlook.com \
--to=jollys@xilinx.com \
--cc=RAJANV@xilinx.com \
--cc=jannh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.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
all inboxes | Powered by JetHome®