From owner-freebsd-current@freebsd.org Wed Jan 3 00:29:02 2018 Return-Path: Delivered-To: freebsd-current@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 8FE7EE82E84 for ; Wed, 3 Jan 2018 00:29:02 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6359D7AAE4 for ; Wed, 3 Jan 2018 00:29:02 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id WWqlezOMyS7BpWWqmeNfGq; Tue, 02 Jan 2018 17:24:10 -0700 X-Authority-Analysis: v=2.2 cv=NKylwwyg c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=RgaUWeydRksA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=zxA2vyXaAAAA:8 a=DjmawdlsAAAA:8 a=6pCwMFOjS23r3FQTQlgA:9 a=pg4Z6IyG5yruRzWy:21 a=qC-V7iTMPdGOpj0R:21 a=CjuIK1q_8ugA:10 a=VNsLjGsGOZnTcv74ccgA:9 a=ZhtNsbIxDLB1L36W:21 a=BYMB9Ud3sxP5vqAt:21 a=8qy8v9n4PZQ8CTHH:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=nK2txNHJmq7TfjpuLlwI:22 a=9WNRskb1zeeanTosM84Z:22 Received: from [25.172.217.252] (S0106d4ca6d8943b0.gv.shawcable.net [70.66.132.207]) by spqr.komquats.com (Postfix) with ESMTPSA id 07E942E0; Tue, 2 Jan 2018 16:24:06 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: Intel CPU design flaw - FreeBSD affected? Date: Tue, 2 Jan 2018 16:24:17 -0800 To: Zaphod Beeblebrox , Michael Butler CC: FreeBSD Current Message-Id: <20180103002407.07E942E0@spqr.komquats.com> X-CMAE-Envelope: MS4wfHDQeK+UiXBmsXE+eg8KDvH5FXkzhlG9G2jQrdVS1ITCjR/YZ54l4aN74J2nV35/cbI3JeBSu98f5gT5hVDOHCAMgsFv1mZ8+kxr+HVRATXvcmbNj+Yc 7H+P2HeVPHttUNE5hQCWVaUWmdrIXotfChRGV536EndbD/GG5FpEXGUSRaksdcBAnzeqPxCyfbW9kFHLRJSTq+pyRaf1SrEAld0zVa/wzPGEHWfo+SFkG9zW oZgGHMLc+PBPIHxFg/DhhA2Gjp0bz1Y8A6dcOzAQ2y4= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2018 00:29:02 -0000 --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Zaphod Beeblebrox Sent: 02/01/2018 15:50 To: Michael Butler Cc: FreeBSD Current Subject: Re: Intel CPU design flaw - FreeBSD affected? >From the information that was leaked by AMD claiming that their processors didn't have the flaws, it would seem any OS in which the kernel occupies the same address space as the userland would be vulnerable. The AMD post implied that Intel's speculative execution of code did not check the validity of the operands before speculatively executing the code. I suppose the implication is that the security check "catches up" with the speculative execution at some point ... and that their (AMD's) microcode did check. Anyways... for those keeping score at home, this is a privilege escalation bug... so it's only really useful in concert with other bugs ... but still pretty huge. Some estimate that between 5% and 30% performance degradation may be unavoidable. Some say it's worse or can't be fully fixed. Certainly, the sunk cost of current CPUs is a huge issue for server farm vendors like Amazon and/or google. On Tue, Jan 2, 2018 at 6:13 PM, Michael Butler wrote: > Has any impact assessment been made as to FreeBSD's exposure or > mitigation strategies? > > 'Kernel memory leaking' Intel processor design flaw forces Linux, > Windows redesign - The Register > > https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ > > _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"