All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm <kvm@vger.kernel.org>,
	Alex Williamson <Alex.Williamson@redhat.com>,
	Chris Wright <chrisw@redhat.com>
Subject: Re: KVM device assignment and user privileges
Date: Sun, 20 Nov 2011 17:15:36 +0200	[thread overview]
Message-ID: <4EC91998.7030704@redhat.com> (raw)
In-Reply-To: <1321801112.3231.8.camel@lappy>

On 11/20/2011 04:58 PM, Sasha Levin wrote:
> Hi all,
>
> I've been working on adding device assignment to KVM tools, and started
> with the basics of just getting a device assigned using the
> KVM_ASSIGN_PCI_DEVICE ioctl.
>
> What I've figured is that unprivileged users can request any PCI device
> to be assigned to him, including devices which he shouldn't be touching.
>
> In my case, it happened with the VGA card, where an unprivileged user
> simply called KVM_ASSIGN_PCI_DEVICE with the bus, seg and fn of the VGA
> card and caused the display on the host to go apeshit.
>
> Was it supposed to work this way? 

No, of course not.

> I couldn't find any security checks in
> the code paths of KVM_ASSIGN_PCI_DEVICE and it looks like any user can
> invoke it with any parameters he'd want - enabling him to kill the host.

Alex, Chris?



-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-11-20 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 14:58 KVM device assignment and user privileges Sasha Levin
2011-11-20 15:15 ` Avi Kivity [this message]
2011-11-21  4:42   ` Chris Wright
2011-11-21  8:32     ` Avi Kivity

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=4EC91998.7030704@redhat.com \
    --to=avi@redhat.com \
    --cc=Alex.Williamson@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.