From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [PATCH bpf] bpf: prevent out-of-bounds speculation Date: Wed, 17 Jan 2018 13:56:14 +0000 Message-ID: <1516197374.4184.5.camel@linux.intel.com> References: <20180105042242.1569490-1-ast@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Daniel Borkmann , Jann Horn , Linus Torvalds , Dan Williams , Mark Rutland , Peter Zijlstra , Elena Reshetova , netdev@vger.kernel.org, kernel-team@fb.com To: Alexei Starovoitov , "David S . Miller" Return-path: Received: from mga06.intel.com ([134.134.136.31]:26566 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752941AbeAQN4n (ORCPT ); Wed, 17 Jan 2018 08:56:43 -0500 In-Reply-To: <20180105042242.1569490-1-ast@kernel.org> Sender: netdev-owner@vger.kernel.org List-ID: > That fixes bpf side of "Variant 1: bounds check bypass (CVE-2017- > 5753)" on > all architectures with and without JIT. For Intel we believe this is true for all family 6 Core, Atom and Knights processors. If that ceases to be the case in future then Intel will provide guidance beforehand. For non x86 you need to check what level of data speculation anyone is doing. I know some Power did data speculation. Your statement may well be true but it would be nice to see AMD, ARM, Power, Sparc etc acks on it. Alan