Date: Sat, 6 Jan 2018 13:37:17 -0800 From: Freddie Cash <fjwcash@gmail.com> To: Freebsd Security <freebsd-security@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Intel hardware bug Message-ID: <CAOjFWZ447V-nwEOpEyoGAkhTyamssrpM1imoZgd7tFmauugKpw@mail.gmail.com> In-Reply-To: <20180106195510.GH75576@funkthat.com> References: <20180105191145.404BC335@spqr.komquats.com> <CAOjFWZ6cJ8C%2BhuRukZ39pW%2B7dkfZmZaC81YkXS6OovX9PB6XbQ@mail.gmail.com> <20180106195510.GH75576@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 6, 2018 11:55 AM, "John-Mark Gurney" <jmg@funkthat.com> wrote: Freddie Cash wrote this message on Fri, Jan 05, 2018 at 11:53 -0800: > Spectre (aka CVE-2017-5715 and CVE-2017-5753) is the issue that affects all > CPUs (Intel, AMD, ARM, IBM, Oracle, etc) and allows userland processes to > read memory assigned to other userland processes (but does NOT give access > to kernel memory). No, Spectre does not allow one userland process to read another userland process's memory.. It allows an attacker to read any memory within the same process. That's variant 1 of Spectre. Variant 2 crosses process boundaries. It's the one that has VM hosting systems worried as a process running in VM1 can read memory assigned to VM2. Cheers, Freddie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ447V-nwEOpEyoGAkhTyamssrpM1imoZgd7tFmauugKpw>