All of lore.kernel.org
 help / color / mirror / Atom feed
From: procmem <procmem@riseup.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: Nethammer and kernel network drivers
Date: Sat, 2 Jun 2018 13:57:24 +0000	[thread overview]
Message-ID: <db41b7e2-cf14-51e3-a2f7-12cffc467bdf@riseup.net> (raw)
In-Reply-To: <20180602094327.GA16667@kroah.com>

Hi. I asked one of the authors (Daniel Gruss) to give you more
insightful feedback as its more helpful in the matter.


Greg KH:
> On Sat, Jun 02, 2018 at 03:46:19AM +0000, procmem wrote:
>> Hello. I wanted to get your attention about a new, more serious
>> reincarnation of rowhammer called nethammer that doesn't need to execut
>> any code on the system like in the past nor does it leave a trace.
>>
>> 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.
>>
>> In absence of hardware mitigations, please identify and disable/fix
>> susceptible network drivers to avoid this type of attack. Thanks.
> 
> Any hint as to how to identify such drivers?  Have you looked into what
> this would entail?
> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2018-06-02 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  3:46 Nethammer and kernel network drivers procmem
2018-06-02  9:43 ` Greg KH
2018-06-02 13:57   ` procmem [this message]
2018-06-02 17:41     ` procmem
2018-06-03  6:31       ` Greg KH
2018-06-03 13:23         ` procmem
2018-06-03 13:37           ` Greg KH

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=db41b7e2-cf14-51e3-a2f7-12cffc467bdf@riseup.net \
    --to=procmem@riseup.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-hardening@lists.openwall.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.