netdev - Re: [PATCH v2] bpf: fix check of allowed specifiers in bpf_trace

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 for Android: free password hash cracker in your pocket

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

Message-ID: <85a08645-453b-78ad-e401-55d2894fa64a@iogearbox.net>
Date:   Fri, 23 Nov 2018 21:57:48 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Martynas Pumputis <m@...bda.lt>, netdev@...r.kernel.org
Cc:     ast@...nel.org
Subject: Re: [PATCH v2] bpf: fix check of allowed specifiers in
 bpf_trace_printk

On 11/23/2018 05:43 PM, Martynas Pumputis wrote:
> A format string consisting of "%p" or "%s" followed by an invalid
> specifier (e.g. "%p%\n" or "%s%") could pass the check which
> would make format_decode (lib/vsprintf.c) to warn.
> 
> Reported-by: syzbot+1ec5c5ec949c4adaa0c4@...kaller.appspotmail.com
> Signed-off-by: Martynas Pumputis <m@...bda.lt>

Applied to bpf, thanks!