qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Guerreiro <maxime.guerreiro@gmail.com>
To: qemu-devel@nongnu.org
Subject: What are the security risks of running QEMU/KVM as root?
Date: Tue, 25 Aug 2020 14:46:47 +0200	[thread overview]
Message-ID: <CAPESWZNaFZB-4hk0GNQAbt=KKf9ZzAMON5oLw6WFBUsi_ApkkQ@mail.gmail.com> (raw)

Hello,

I'd be interested to learn more about the security 'vision' of qemu/kvm being
two components, one running in-kernel, one running in user land. What are the
security advantages of running guests as non-root?

In case of a qemu or KVM vulnerability, won't malicious guests gain kernel
privilege no matter what user is running qemu?

If a guest is able to execute arbitrary code as the "qemu" user, can
it escalate to
root privileges using /dev/kvm?

I've also asked this on StackExchange [1], for visibility.

Thanks,
Maxime

[1]: https://security.stackexchange.com/questions/236681/what-are-the-security-risks-of-running-qemu-kvm-as-root


                 reply	other threads:[~2020-08-25 13:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPESWZNaFZB-4hk0GNQAbt=KKf9ZzAMON5oLw6WFBUsi_ApkkQ@mail.gmail.com' \
    --to=maxime.guerreiro@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).