From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Wenwen Wang <wang6495@umn.edu>, Wenwen Wang <wang6495@umn.edu>
Cc: Kangjie Lu <kjlu@umn.edu>, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] stm class: fix a missing-check bug
Date: Wed, 03 Oct 2018 10:56:40 +0300 [thread overview]
Message-ID: <87h8i379af.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <1538542259-11868-1-git-send-email-wang6495@umn.edu>
Wenwen Wang <wang6495@umn.edu> writes:
> In stm_char_policy_set_ioctl(), the 'size' field of the struct
> 'stp_polic_id' is firstly copied from the user space and then checked,
> because the length of the 'id' field in this struct, which represents an
> identification string, is not fixed. If the 'size' field cannot pass the
> check, an error code EINVAL will be returned. However, after the check, the
> whole struct is copied again from the user space. Given that the user data
> resides in the user space, a malicious user-space process can race to
> change the size between the two copies. By doing so, the attacker can
> bypass the check on the 'size' field and inject malicious data.
How? The id->size is not used for anything.
And even if there was a problem, this:
> - if (copy_from_user(id, arg, size)) {
> + if (copy_from_user(&id->master, (char __user *)arg + sizeof(size),
> + size - sizeof(size))) {
is completely pointless.
> ret = -EFAULT;
> goto err_free;
> }
>
> + id->size = size;
So, if we did use id->size after the copying, we'd indeed have this line
in the code. But since we don't, it's also pointless, so it's not there.
Thanks,
--
Alex
next prev parent reply other threads:[~2018-10-03 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 4:50 Wenwen Wang
2018-10-03 7:56 ` Alexander Shishkin [this message]
2018-10-03 14:54 ` Wenwen Wang
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=87h8i379af.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=wang6495@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
all inboxes | Powered by JetHome®