qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: procmem <procmem@riseup.net>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, whonix-devel@whonix.org,
	jasowang@redhat.com
Subject: Re: [Qemu-devel] Virtio-net drivers immune to Nethammer?
Date: Fri, 1 Jun 2018 18:58:20 +0300	[thread overview]
Message-ID: <20180601184855-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <b25b3adb-bacc-bef1-7d18-c71a4933abc1@riseup.net>

On Fri, Jun 01, 2018 at 01:15:44PM +0000, procmem wrote:
> 
> 
> Stefan Hajnoczi:
> > On Mon, May 21, 2018 at 11:24:43PM +0000, procmem wrote:
> >> Hi I'm a privacy distro maintainer investigating the implications of the
> >> newly published nethammer attack [0] on KVM guests particularly the
> >> virtio-net drivers. The summary of the paper is that rowhammer can be
> >> remotely triggered by feeding susceptible* network driver crafted
> >> traffic. This attack can do all kinds of nasty things such as modifying
> >> SSL certs on the victim system.
> >>
> >> * Susceptible drivers are those relying on Intel CAT, uncached memory or
> >> the clflush instruction.
> >>
> >> My question is, do virtio-net drivers do any of these things?
> > I have CCed Michael Tsirkin and Jason Wang, the virtio maintainers.
> > 
> >> ***
> >>
> >> [0] https://arxiv.org/abs/1805.04956
> >>
> >>
> >>
> 
> Thanks :) I thought my message was forgotten


I don't think virtio is using either of these.

Linux does support CAT AFAIK but it has nothing to do with virtio.

-- 
MST

  reply	other threads:[~2018-06-01 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 23:24 [Qemu-devel] Virtio-net drivers immune to Nethammer? procmem
2018-06-01 11:34 ` Stefan Hajnoczi
2018-06-01 13:15   ` procmem
2018-06-01 15:58     ` Michael S. Tsirkin [this message]
2018-06-01 18:54       ` Dr. David Alan Gilbert
2018-06-02  3:04         ` procmem
2018-06-02  3:08       ` procmem
2018-06-03 16:10         ` Michael S. Tsirkin

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=20180601184855-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=procmem@riseup.net \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=whonix-devel@whonix.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).