[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28363c0d-0b78-681c-d9ea-908671b0067e@iogearbox.net>
Date: Fri, 4 May 2018 02:16:31 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Mark Rutland <mark.rutland@....com>, linux-kernel@...r.kernel.org
Cc: Alexei Starovoitov <ast@...nel.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Peter Zijlstra <peterz@...radead.org>, netdev@...r.kernel.org
Subject: Re: [PATCH] bpf: fix possible spectre-v1 in find_and_alloc_map()
On 05/03/2018 06:04 PM, Mark Rutland wrote:
> It's possible for userspace to control attr->map_type. Sanitize it when
> using it as an array index to prevent an out-of-bounds value being used
> under speculation.
>
> Found by smatch.
>
> Signed-off-by: Mark Rutland <mark.rutland@....com>
> Cc: Alexei Starovoitov <ast@...nel.org>
> Cc: Dan Carpenter <dan.carpenter@...cle.com>
> Cc: Daniel Borkmann <daniel@...earbox.net>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: netdev@...r.kernel.org
Applied to bpf tree, thanks Mark! I've also just submitted one for
BPF progs (http://patchwork.ozlabs.org/patch/908385/) which is same
situation.
Powered by blists - more mailing lists