From owner-freebsd-security@freebsd.org Tue Mar 20 21:00:08 2018 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E95DDF46784 for ; Tue, 20 Mar 2018 21:00:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 870A48751E for ; Tue, 20 Mar 2018 21:00:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from localhost by mail.inka.de with local-rmail id 1eyOMX-00065l-Ij; Tue, 20 Mar 2018 22:00:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w2KKuhwZ086186 for ; Tue, 20 Mar 2018 21:56:43 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w2KKuhOj086185 for freebsd-security@freebsd.org; Tue, 20 Mar 2018 21:56:43 +0100 (CET) (envelope-from news) To: freebsd-security@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.security Subject: Re: FreeBSD Security Advisory FreeBSD-SA-18:03.speculative_execution Date: Tue, 20 Mar 2018 20:56:43 -0000 (UTC) Message-ID: References: <20180314042924.E880D1128@freefall.freebsd.org> <337d9fd4-2aa4-609a-6a00-e9ce2be599cc@netfence.it> <8deba9d2-17b5-9088-1766-42f9e334df89@demter.de> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 21:00:08 -0000 On 2018-03-19, Ed Maste wrote: > There's one small wrinkle: there are some recent lower-end processors > (at least some recent Celerons) which it seems are not susceptible to > Meltdown, and after a microcode update will set a bit to indicate > this. Specifically, Goldmont cores (Apollo Lake, Denverton). -- Christian "naddy" Weisgerber naddy@mips.inka.de