From: Stefan Hajnoczi <stefanha@gmail.com>
To: procmem <procmem@riseup.net>
Cc: qemu-devel@nongnu.org, whonix-devel@whonix.org,
"Michael S. Tsirkin" <mst@redhat.com>,
jasowang@redhat.com
Subject: Re: [Qemu-devel] Virtio-net drivers immune to Nethammer?
Date: Fri, 1 Jun 2018 12:34:44 +0100 [thread overview]
Message-ID: <20180601113444.GG8687@stefanha-x1.localdomain> (raw)
In-Reply-To: <40602400-cae4-e175-e7ce-10ac70ba52f5@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
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
>
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-06-01 11:34 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 [this message]
2018-06-01 13:15 ` procmem
2018-06-01 15:58 ` Michael S. Tsirkin
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=20180601113444.GG8687@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=procmem@riseup.net \
--cc=qemu-devel@nongnu.org \
--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 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.