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  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]
Date:   Thu, 14 May 2020 12:21:52 +0200
From:   Daniel Borkmann <>
To:     David Laight <David.Laight@...LAB.COM>,
        Al Viro <>
Cc:     Christoph Hellwig <>,
        Linus Torvalds <>,
        the arch/x86 maintainers <>,
        Alexei Starovoitov <>,
        Masami Hiramatsu <>,
        Andrew Morton <>,
        "" <>,
        linux-um <>,
        Netdev <>,
        "" <>,
        Linux-MM <>,
        Linux Kernel Mailing List <>,
        "" <>
Subject: Re: [PATCH 11/18] maccess: remove strncpy_from_unsafe

On 5/14/20 12:01 PM, David Laight wrote:
> If it's not a stupid question why is a BPF program allowed to get
> into a situation where it might have an invalid kernel address.
> It all stinks of a hole that allows all of kernel memory to be read
> and copied to userspace.
> Now you might want to something special so that BPF programs just
> abort on OOPS instead of possibly paniking the kernel.
> But that is different from a copy that expects to be passed garbage.

I suggest you read up on probe_kernel_read() and its uses in tracing in
general, looks like you haven't done that.

Powered by blists - more mailing lists