From owner-freebsd-security@freebsd.org  Thu Jan  4 02:36:57 2018
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA95BEBFFA6
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu,  4 Jan 2018 02:36:57 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id B40F0748EA;
 Thu,  4 Jan 2018 02:36:57 +0000 (UTC) (envelope-from des@des.no)
Received: from desk.des.no (smtp.des.no [194.63.250.102])
 by smtp.des.no (Postfix) with ESMTP id 8B1421045D;
 Thu,  4 Jan 2018 02:36:56 +0000 (UTC)
Received: by desk.des.no (Postfix, from userid 1001)
 id 229E65CDAB; Thu,  4 Jan 2018 02:35:24 +0000 (UTC)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: "David M. Syzdek" <david.syzdek@acsalaska.net>
Cc: Eric van Gyzen <vangyzen@FreeBSD.org>,
 "freebsd-security\@freebsd.org" <freebsd-security@freebsd.org>,
 "Ronald F. Guilmette" <rfg@tristatelogic.com>
Subject: Re: Intel hardware bug
References: <19097.1515012519@segfault.tristatelogic.com>
 <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org>
 <7C58A6DB-0760-4E5A-B65D-2ED6A6B7AAD2@acsalaska.net>
Date: Thu, 04 Jan 2018 03:35:24 +0100
In-Reply-To: <7C58A6DB-0760-4E5A-B65D-2ED6A6B7AAD2@acsalaska.net> (David
 M. Syzdek's message of "Wed, 3 Jan 2018 13:43:08 -0900")
Message-ID: <867esy2vwz.fsf@desk.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 02:36:58 -0000

"David M. Syzdek" <david.syzdek@acsalaska.net> writes:
> They did not say it is *NOT* a bug, just that it is not a bug unique
> to Intel.  [...] Additionally, they indirectly imply that both AMD and
> ARM chips are affected by the same bug, however this is, at least in
> AMD=E2=80=99s case, appears to be directly refuted [...] by AMD:

There are three different issues.  One of them (CVE-2017-5754, labeled
=E2=80=9CMeltdown=E2=80=9D) is easily mitigated and has so far only been sh=
own to affect
Intel processors.  The other two (CVE-2017-5753 and CVE-2017-5715,
collectively labeled =E2=80=9CSpectre=E2=80=9D) affect AMD and ARM processo=
rs as well
and have no known workaround.

So far, it has been shown that an unprivileged process can read data
from the kernel (Meltdown) and other processes (Spectre), and that a
privileged process in a VM can read data from the host and presumably
also from other VMs on the same host (Spectre).

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no