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

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

Message-ID: <20181219210101.214574-1-kafai@fb.com>
Date:   Wed, 19 Dec 2018 13:01:01 -0800
From:   Martin KaFai Lau <kafai@...com>
To:     <netdev@...r.kernel.org>
CC:     Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>, <kernel-team@...com>
Subject: [PATCH bpf-next 0/2] Ensure line_info.insn_off cannot point to insn with zero code

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.

Martin KaFai Lau (2):
  bpf: Ensure line_info.insn_off cannot point to insn with zero code
  bpf: Add BPF_LD_IMM64 to the line_info test

 kernel/bpf/verifier.c                  |  8 ++++++++
 tools/testing/selftests/bpf/test_btf.c | 27 ++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)

-- 
2.17.1