netdev - Re: [PATCH] bpf: fix possible spectre-v1 in find_and_alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180503.124847.1815876480542537219.davem@davemloft.net>
Date:   Thu, 03 May 2018 12:48:47 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     mark.rutland@....com
Cc:     linux-kernel@...r.kernel.org, ast@...nel.org,
        dan.carpenter@...cle.com, daniel@...earbox.net,
        peterz@...radead.org, netdev@...r.kernel.org
Subject: Re: [PATCH] bpf: fix possible spectre-v1 in find_and_alloc_map()

From: Mark Rutland <mark.rutland@....com>
Date: Thu,  3 May 2018 17:04:59 +0100

> 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>

Acked-by: David S. Miller <davem@...emloft.net>