netdev - Re: [PATCH bpf-next 0/2] Ensure line_info.insn_off cannot point to insn with zero code

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] [day] [month] [year] [list]

Message-ID: <20181219234623.xnru4vjpzvdmnlqi@ast-mbp.dhcp.thefacebook.com>
Date:   Wed, 19 Dec 2018 15:46:24 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Martin KaFai Lau <kafai@...com>
Cc:     netdev@...r.kernel.org, Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>, kernel-team@...com
Subject: Re: [PATCH bpf-next 0/2] Ensure line_info.insn_off cannot point to
 insn with zero code

On Wed, Dec 19, 2018 at 01:01:01PM -0800, Martin KaFai Lau wrote:
> This series ensures the line_info (passed by the userspace during
> bpf_prog_load) cannot have its line_info.insn_off pointing to a
> zero bpf insn code.  F.e. a broken userspace tool might
> generate a line_info.insn_off that points to the second
> 8 bytes of a BPF_LD_IMM64.
> 
> The first patch is the kernel change.
> The second patch is a new test case.

Applied, Thanks