From owner-freebsd-security@freebsd.org  Fri Jan  5 15:53:01 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 BABB9EB0A16;
 Fri,  5 Jan 2018 15:53:01 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from mail.metricspace.net (mail.metricspace.net
 [IPv6:2001:470:1f11:617::107])
 by mx1.freebsd.org (Postfix) with ESMTP id 921806F00F;
 Fri,  5 Jan 2018 15:53:01 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from [192.168.43.57] (mobile-166-171-187-244.mycingular.net
 [166.171.187.244])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate) (Authenticated sender: eric)
 by mail.metricspace.net (Postfix) with ESMTPSA id 1FE5D8900;
 Fri,  5 Jan 2018 15:35:14 +0000 (UTC)
Subject: Re: Intel hardware bug
To: =?UTF-8?Q?C_Bergstr=c3=b6m?= <cbergstrom@pathscale.com>
Cc: Freebsd Security <freebsd-security@freebsd.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>,
 FreeBSD Hackers <freebsd-hackers@freebsd.org>
References: <736a2b77-d4a0-b03f-8a6b-6a717f5744d4@metricspace.net>
 <2594.1515141192@segfault.tristatelogic.com>
 <809675000.867372.1515146821354@mail.yahoo.com>
 <250f3a77-822b-fba5-dcd7-758dfec94554@metricspace.net>
 <CAOnawYpe5V-kUn4tLWKyBcDmsKqUP9-VNRhfDG48VMFWFbq6Vw@mail.gmail.com>
From: Eric McCorkle <eric@metricspace.net>
Message-ID: <755a65eb-b02e-05c5-e1a2-701cfd8bc837@metricspace.net>
Date: Fri, 5 Jan 2018 10:35:13 -0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAOnawYpe5V-kUn4tLWKyBcDmsKqUP9-VNRhfDG48VMFWFbq6Vw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
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: Fri, 05 Jan 2018 15:53:01 -0000

On 01/05/2018 09:55, C Bergström wrote:

>     Don't bet on it.  There's reports of AMD vulnerabilities, also for ARM.
>     I doubt any major architecture is going to make it out unscathed.  (But
>     if one does, my money's on Power)
> 
> 
> Nope, the only arch that I'm aware of that gets past this is SPARC(hah!)
> due to the seperate userland and kernel memory virtualization.

Alas, poor Sparc.  I knew them, Horatio...

It looks like Red Hat is indeed reporting Power9 to be vulnerable:

https://access.redhat.com/security/vulnerabilities/speculativeexecution

Unfortunate.  I hope they get fixed silicon out in time for the Talos II
workstation.