From owner-freebsd-security@freebsd.org Wed May 15 14:34:44 2019 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 71B3A159363D for ; Wed, 15 May 2019 14:34:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 160BA8DE89; Wed, 15 May 2019 14:34:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id A3D87F111; Wed, 15 May 2019 14:34:43 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f49.google.com with SMTP id q17so10244lfo.4; Wed, 15 May 2019 07:34:43 -0700 (PDT) X-Gm-Message-State: APjAAAXjgzgjd9CWISVqZqqVr0DUuUayXNmbBUzNsGo+4eEVmOXb6wm3 7jQ+VHX6Qraxaois9eb+AHxLtG0CP0hOi6azE90= X-Google-Smtp-Source: APXvYqz5jChxJGn4Xd389HHEggXBoRQmOfL12MIIzfrX+AW7EKiJfvaZqrn/hyubLWgxPPhEUiq/P6t3/jkqfwZFNcU= X-Received: by 2002:ac2:4315:: with SMTP id l21mr20109764lfh.143.1557930882287; Wed, 15 May 2019 07:34:42 -0700 (PDT) MIME-Version: 1.0 References: <20190515000302.44CBB1AB79@freefall.freebsd.org> <31b178d5-9998-d2a3-cc4c-d3f7d574743a@sentex.net> In-Reply-To: <31b178d5-9998-d2a3-cc4c-d3f7d574743a@sentex.net> From: Kyle Evans Date: Wed, 15 May 2019 09:33:50 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-19:07.mds To: mike tancsa Cc: "Wall, Stephen" , "freebsd-security@freebsd.org" , Mark Johnston Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 160BA8DE89 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.96)[-0.960,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-Mailman-Approved-At: Wed, 15 May 2019 16:34:48 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 14:34:44 -0000 On Wed, May 15, 2019 at 8:33 AM mike tancsa wrote: > > On 5/15/2019 8:18 AM, Wall, Stephen wrote: > >> New CPU microcode may be available in a BIOS update from your system vendor, > >> or by installing the devcpu-data package or sysutils/devcpu-data port. > >> Ensure that the BIOS update or devcpu-data package is dated after 2014-05-14. > >> > >> If using the package or port the microcode update can be applied at boot time > >> by adding the following lines to the system's /boot/loader.conf: > >> > >> cpu_microcode_load="YES" > >> cpu_microcode_name="/boot/firmware/intel-ucode.bin" > > Is this applicable in a virtualized environment, or only on bare metal? > > If not applicable in a VM, is it at least harmless? > > > Actually, just tried this on RELENG_11 (r347613) and I get > > don't know how to load module '/boot/firmware/intel-ucode.bin' > > In boot/loader.conf I have > > cpu_microcode_load="YES" > cpu_microcode_name="/boot/firmware/intel-ucode.bin" > > # ls -l /boot/firmware/intel-ucode.bin > -rw-r--r-- 1 root wheel uarch 2571264 May 15 08:47 > /boot/firmware/intel-ucode.bin > > # sha256 /boot/firmware/intel-ucode.bin > SHA256 (/boot/firmware/intel-ucode.bin) = > 1fdb3a25467d285394eded8039ee8ab488f074903654981d35a4cdfe6ebf12fc > r337715 + r337716 were responsible for making this work, and they've not yet been MFC'd as far as I can tell. CC markj@, because that's probably good to sneak in soon.