From owner-freebsd-current@freebsd.org Tue Jan 2 23:50:00 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 55020E80E0B for ; Tue, 2 Jan 2018 23:50:00 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAAB5794AF for ; Tue, 2 Jan 2018 23:49:59 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id g75so6026wme.0 for ; Tue, 02 Jan 2018 15:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+EMr8bfaJDn6o8vyDq0IqBextpp0MGK77r9Wklk+WkA=; b=tE/8+htv3cyKgrPftr07DOKs/cl2VZgbHeG4iTI58hibCn+yoxlwcl6BmszT1+D7L8 RCuMau24I3vP1WNlUqVOrZkTFEIX9poikDvx8PsmJm2GW22kO5MkrsP0YiLGdBq5vg7S BokDxiWTu2gxY+QfGya8vG9lyhcYN4hdezMoMsowNWwXOe44kQy0V5qjYIy0Lq77/EKw NmoHVbB7Q7UU93jzTV1m+viIWmoFh2Epv5ndmIUMlHi+XL+SSWJTFjHc3ji5WLsXxPLS 3//ajGV2l/YebaQDxLLqy07DKbMwiJgg6ZYxbEXPimEKF7/B+BubXJIMWxBnaX+W7xjc PCAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+EMr8bfaJDn6o8vyDq0IqBextpp0MGK77r9Wklk+WkA=; b=BkIICnsjnZeqMDTIDbirW1jSIXFRNFqQbSPs6BXeuHS4K5vpjLfpRtMMTM5sqU/rOa hETa2jKCncr4CgXRxI519a6E11F09e9q/pnwXYtuMPdg54eVzAmwllp1fFFj1pgpDyXH sNful6eAyIf6G9M2r6HISiOC2fD69uVtCJV7aErr+45yO9QT4k1eiLWCPDzp2/xLs7vm GHnMq+ydss/KPMsc2+jyGmzGM6HTAmVeRftCEczEFau9i2obE7mxuwMLxbOeEccjs17F tHoOO1Hk47xiZMfgtq7Ii2mB7KFuTtKCVJ+CxjIe96BHDmV1I/9CIO/xMXPz3O3IHnfB V/TQ== X-Gm-Message-State: AKGB3mLI/x68JmtxgWKnGmQiWXpVuF7xethNJzX30idnaWtK1gjVnetY xeSB+DVZqEM2YX72ShqbFIBpfCDiGSa6j9yHHw== X-Google-Smtp-Source: ACJfBotZECQauDC+XALdgD/rFnXim6JsKPsS3zU6COz/wxdcdN3gYJSI71WWLGcFaTo713siOaRb1xze6c6N6PFzB94= X-Received: by 10.80.165.109 with SMTP id z42mr74419edb.18.1514936998261; Tue, 02 Jan 2018 15:49:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.181.59 with HTTP; Tue, 2 Jan 2018 15:49:57 -0800 (PST) In-Reply-To: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> From: Zaphod Beeblebrox Date: Tue, 2 Jan 2018 18:49:57 -0500 Message-ID: Subject: Re: Intel CPU design flaw - FreeBSD affected? To: Michael Butler Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" 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: Tue, 02 Jan 2018 23:50:00 -0000 >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/ > >