linux-kernel - Re: Spectre mitigation doesn't seem to work at all?!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180604091509.GP12217@hirez.programming.kicks-ass.net>
Date:   Mon, 4 Jun 2018 11:15:09 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Andreas Hartmann <andihartmann@...enet.de>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: Spectre mitigation doesn't seem to work at all?!

On Mon, Jun 04, 2018 at 10:50:07AM +0200, Andreas Hartmann wrote:

> Ok, this means every program running on the machine has to care itself
> to be spectre v1 - safe.

Correct. Compiler and static analyser teams are looking hard at this to
help.

> A malicious program most probably won't care about that. Therefore, my
> next question is: which memory regions can be exploited by a malicious
> program? The complete physical memory or only the memory provided to the
> malicious program? Should be the latter if this approach should have any
> impact.

It affects the virtual memory of the target process.