From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kangjie Lu <kjlu@umn.edu>
Cc: pakki001@umn.edu, Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: property: fix a buffer overflow and a missing check
Date: Mon, 25 Mar 2019 12:01:04 +0200 [thread overview]
Message-ID: <20190325100104.GE3622@lahna.fi.intel.com> (raw)
In-Reply-To: <20190324224916.1389-1-kjlu@umn.edu>
On Sun, Mar 24, 2019 at 05:49:16PM -0500, Kangjie Lu wrote:
> First, no memory is allocated for "property->value.text"; the
> following strcpy will lead to a buffer overflow.
It is actually member of union so assigning via value.txt or value.data
is the same.
So no buffer overflow.
> Second, no check is enforced for the return value of kzalloc,
> which may lead to NULL-pointer dereference.
Yes, this is valid.
Can you fix the changelog accordingly and resend?
>
> The patch fixes the two issues.
>
> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
> ---
> drivers/thunderbolt/property.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/thunderbolt/property.c b/drivers/thunderbolt/property.c
> index 841314deb446..d5b0cdb8f0b1 100644
> --- a/drivers/thunderbolt/property.c
> +++ b/drivers/thunderbolt/property.c
> @@ -587,7 +587,12 @@ int tb_property_add_text(struct tb_property_dir *parent, const char *key,
> return -ENOMEM;
>
> property->length = size / 4;
> - property->value.data = kzalloc(size, GFP_KERNEL);
> + property->value.text = kzalloc(size, GFP_KERNEL);
> + if (!property->value.text) {
> + kfree(property);
> + return -ENOMEM;
> + }
> +
> strcpy(property->value.text, text);
>
> list_add_tail(&property->list, &parent->properties);
> --
> 2.17.1
next prev parent reply other threads:[~2019-03-25 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 22:49 [PATCH] thunderbolt: property: fix a buffer overflow and a missing check Kangjie Lu
2019-03-25 10:01 ` Mika Westerberg [this message]
2019-03-27 14:45 ` Mukesh Ojha
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=20190325100104.GE3622@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=pakki001@umn.edu \
/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