LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Wenwen Wang <wang6495@umn.edu>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Kangjie Lu <kjlu@umn.edu>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
Wenwen Wang <wang6495@umn.edu>
Subject: Re: [PATCH] virt: vbox: fix a missing-check bug
Date: Tue, 8 May 2018 07:52:57 -0500 [thread overview]
Message-ID: <CAAa=b7fkdwTF7tU1si-J3k00kcRze54QJfdrWX45wTWgYAXzmg@mail.gmail.com> (raw)
In-Reply-To: <8db08d8e-c618-d806-b824-0b8990ef0785@redhat.com>
On Tue, May 8, 2018 at 6:46 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi Wenwen,
>
> On 06-05-18 05:30, Wenwen Wang wrote:
>>
>> In vbg_misc_device_ioctl(), the header of the ioctl argument is copied
>> from
>> the userspace pointer 'arg' and saved to the kernel object 'hdr'. Then the
>> 'version', 'size_in', and 'size_out' fields of 'hdr' are verified. For
>> example, if 'hdr.version' is not VBG_IOCTL_HDR_VERSION, an error code
>> -EINVAL will be returned. If 'hdr' can pass all verifications, the whole
>> structure of the ioctl argument is copied once again from 'arg' and saved
>> to 'buf'. Then the function vbg_core_ioctl() is invoked to execute the
>> ioctl command. Given that the 'arg' pointer resides in userspace, a
>> malicious userspace process can race to change the data pointed to by
>> 'arg'
>> between the two copies. By doing so, the user can bypass the verifications
>> on the ioctl argument, which can cause vbg_core_ioctl() to work on
>> unsecure
>> data because it assumes the 'version', 'size_in', and 'size_out' have been
>> verified by vbg_misc_device_ioctl(), as mentioned in the comment in
>> vbg_core_ioctl():
>>
>> /*
>> * hdr->version and hdr->size_in / hdr->size_out minimum size are
>> * already checked by vbg_misc_device_ioctl().
>> */
>>
>> This patch adds checks after the second copy to ensure the consistency
>> between the data obtained in the two copies. In case an inconsistency is
>> detected, an error code -EINVAL will be returned.
>>
>> Signed-off-by: Wenwen Wang <wang6495@umn.edu>
>
>
> Thank you for finding this. I don't think that doing a second check is
> a good solution, by copy and pasting the checks we run the risk that
> any future additional checks are omitted from one copy of the checks.
>
> Instead I think we should simply avoid the 2nd copy of the header, like
> this:
>
> From 0c50b0dce3cf25a0ee9794c5816d9a0232d29e0a Mon Sep 17 00:00:00 2001
> From: Hans de Goede <hdegoede@redhat.com>
> Date: Tue, 8 May 2018 13:23:01 +0200
> Subject: [PATCH 3/3] virt: vbox: Only copy_from_user the request-header once
>
> In vbg_misc_device_ioctl(), the header of the ioctl argument is copied from
> the userspace pointer 'arg' and saved to the kernel object 'hdr'. Then the
> 'version', 'size_in', and 'size_out' fields of 'hdr' are verified.
>
> Before this commit, after the checks a buffer for the entire request would
> be allocated and then all data including the verified header would be
> copied from the userspace 'arg' pointer again.
>
> Given that the 'arg' pointer resides in userspace, a malicious userspace
> process can race to change the data pointed to by 'arg' between the two
> copies. By doing so, the user can bypass the verifications on the ioctl
> argument.
>
> This commit fixes this by using the already checked copy of the header
> to fill the header part of the allocated buffer and only copying the
> remainder of the data from userspace.
>
> Reported-by: Wenwen Wang <wang6495@umn.edu>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/virt/vboxguest/vboxguest_linux.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/virt/vboxguest/vboxguest_linux.c
> b/drivers/virt/vboxguest/vboxguest_linux.c
> index 398d22693234..6e2a9619192d 100644
> --- a/drivers/virt/vboxguest/vboxguest_linux.c
> +++ b/drivers/virt/vboxguest/vboxguest_linux.c
> @@ -121,7 +121,9 @@ static long vbg_misc_device_ioctl(struct file *filp,
> unsigned int req,
> if (!buf)
> return -ENOMEM;
>
> - if (copy_from_user(buf, (void *)arg, hdr.size_in)) {
> + *((struct vbg_ioctl_hdr *)buf) = hdr;
> + if (copy_from_user(buf + sizeof(hdr), (void *)arg + sizeof(hdr),
> + hdr.size_in - sizeof(hdr))) {
> ret = -EFAULT;
> goto out;
> }
>
> Do you agree that this would also fix the race window you found?
Thanks for your response. Yes, this fix also works.
Wenwen
prev parent reply other threads:[~2018-05-08 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 3:30 Wenwen Wang
2018-05-08 11:46 ` Hans de Goede
2018-05-08 12:52 ` Wenwen Wang [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='CAAa=b7fkdwTF7tU1si-J3k00kcRze54QJfdrWX45wTWgYAXzmg@mail.gmail.com' \
--to=wang6495@umn.edu \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] virt: vbox: fix a missing-check bug' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).