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
| ||
|
Date: Fri, 20 Mar 2020 21:07:45 +0100 From: Daniel Borkmann <daniel@...earbox.net> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: Alexei Starovoitov <ast@...nel.org>, Martin KaFai Lau <kafai@...com>, Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>, Andrii Nakryiko <andriin@...com>, netdev@...r.kernel.org, bpf@...r.kernel.org, linux-kernel@...r.kernel.org, Maciej Żenczykowski <maze@...gle.com>, John Stultz <john.stultz@...aro.org>, Alexander Potapenko <glider@...gle.com>, Alistair Delva <adelva@...gle.com> Subject: Re: [PATCH] bpf: explicitly memset some bpf info structures declared on the stack On 3/20/20 5:22 PM, Greg Kroah-Hartman wrote: > Trying to initialize a structure with "= {};" will not always clean out > all padding locations in a structure. So be explicit and call memset to > initialize everything for a number of bpf information structures that > are then copied from userspace, sometimes from smaller memory locations > than the size of the structure. > > Reported-by: Daniel Borkmann <daniel@...earbox.net > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Applied, thanks!
Powered by blists - more mailing lists