bpf: Fix ref_obj_id for dynptr data slices in verifier
Subsystems (4)
PATCH v3 1/2 bpf: Fix ref_obj_id for dynptr data slices in verifier
When a data slice is obtained from a dynptr (through the bpf_dynptr_data API), the ref obj id of the dynptr must be found and then associated with the data slice.
The ref obj id of the dynptr must be found *before* the caller saved regs are reset. Without this fix, the ref obj id tracking is not correct for dynptrs that are at an offset from the frame pointer.
Please also note that the data slice's ref obj id must be assigned after the ret types are parsed, since RET_PTR_TO_ALLOC_MEM-type return regs get zero-marked.
--- kernel/bpf/verifier.c | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-)
kernel/bpf/verifier.c +18 -16
@@ -7342,6 +7342,23 @@ static int check_helper_call(struct bpf_verifier_env *env, struct bpf_insn *insn } }break ; +case BPF_FUNC_dynptr_data: +for (i =0 ; i <MAX_BPF_FUNC_REG_ARGS ; i++) { +if (arg_type_is_dynptr (fn->arg_type[i])) { +if (meta.ref_obj_id) { +verbose (env,"verifier internal error: meta.ref_obj_id already set\n" ); +return -EFAULT ; + } +/* Find the id of the dynptr we're tracking the reference of */ + meta.ref_obj_id =stack_slot_get_id (env, ®s[BPF_REG_1 + i]); +break ; + } + } +if (i ==MAX_BPF_FUNC_REG_ARGS ) { +verbose (env,"verifier internal error: no dynptr in bpf_dynptr_data()\n" ); +return -EFAULT ; + } +break ; }if (err)
@@ -7473,7 +7490,7 @@ static int check_helper_call(struct bpf_verifier_env *env, struct bpf_insn *insnif (type_may_be_null (regs[BPF_REG_0 ].type)) regs[BPF_REG_0 ].id = ++env->id_gen; -if (is_ptr_cast_function (func_id)) { +if (is_ptr_cast_function (func_id) || func_id == BPF_FUNC_dynptr_data) {/* For release_reference() */ regs[BPF_REG_0 ].ref_obj_id = meta.ref_obj_id; }else if (is_acquire_function (func_id, meta.map_ptr)) {
@@ -7485,21 +7502,6 @@ static int check_helper_call(struct bpf_verifier_env *env, struct bpf_insn *insn regs[BPF_REG_0 ].id = id;/* For release_reference() */ regs[BPF_REG_0 ].ref_obj_id = id; - }else if (func_id == BPF_FUNC_dynptr_data) { -int dynptr_id =0 , i; - -/* Find the id of the dynptr we're acquiring a reference to */ -for (i =0 ; i <MAX_BPF_FUNC_REG_ARGS ; i++) { -if (arg_type_is_dynptr (fn->arg_type[i])) { -if (dynptr_id) { -verbose (env,"verifier internal error: multiple dynptr args in func\n" ); -return -EFAULT ; - } - dynptr_id =stack_slot_get_id (env, ®s[BPF_REG_1 + i]); - } - } -/* For release_reference() */ - regs[BPF_REG_0 ].ref_obj_id = dynptr_id; }do_refine_retval_range (regs, fn->ret_type, func_id, &meta);
Signature · 1 line
2.30.2
PATCH v3 2/2 selftests/bpf: add extra test for using dynptr data slice after release
Add an additional test, "data_slice_use_after_release2", for ensuring that data slices are correctly invalidated by the verifier after the dynptr whose ref obj id they track is released. In particular, this tests data slice invalidation for dynptrs located at a non-zero offset from the frame pointer.
--- .../testing/selftests/bpf/prog_tests/dynptr.c | 3 +- .../testing/selftests/bpf/progs/dynptr_fail.c | 38 ++++++++++++++++++- 2 files changed, 39 insertions(+), 2 deletions(-)
tools/testing/selftests/bpf/prog_tests/dynptr.c +2 -1
@@ -22,7 +22,8 @@ static struct { {"add_dynptr_to_map2", "invalid indirect read from stack"}, {"data_slice_out_of_bounds_ringbuf", "value is outside of the allowed memory range"}, {"data_slice_out_of_bounds_map_value", "value is outside of the allowed memory range"}, - {"data_slice_use_after_release", "invalid mem access 'scalar'"}, + {"data_slice_use_after_release1", "invalid mem access 'scalar'"}, + {"data_slice_use_after_release2", "invalid mem access 'scalar'"}, {"data_slice_missing_null_check1", "invalid mem access 'mem_or_null'"}, {"data_slice_missing_null_check2", "invalid mem access 'mem_or_null'"}, {"invalid_helper1", "invalid indirect read from stack"},
tools/testing/selftests/bpf/progs/dynptr_fail.c +37 -1
@@ -248,7 +248,7 @@ int data_slice_out_of_bounds_map_value(void *ctx)/* A data slice can't be used after it has been released */ SEC("?raw_tp") -int data_slice_use_after_release (void *ctx) +int data_slice_use_after_release1 (void *ctx) {struct bpf_dynptr ptr;struct sample *sample;
@@ -272,6 +272,42 @@ int data_slice_use_after_release(void *ctx)return 0 ; } +/* A data slice can't be used after it has been released. +* +* This tests the case where the data slice tracks a dynptr (ptr2) +* that is at a non-zero offset from the frame pointer (ptr1 is at fp, +* ptr2 is at fp - 16). +*/ +SEC("?raw_tp") +int data_slice_use_after_release2 (void *ctx) +{ +struct bpf_dynptr ptr1, ptr2; +struct sample *sample; + +bpf_ringbuf_reserve_dynptr (&ringbuf,64 ,0 , &ptr1); +bpf_ringbuf_reserve_dynptr (&ringbuf,sizeof (*sample),0 , &ptr2); + + sample =bpf_dynptr_data (&ptr2,0 ,sizeof (*sample)); +if (!sample) + goto done; + + sample->pid =23 ; + +bpf_ringbuf_submit_dynptr (&ptr2,0 ); + +/* this should fail */ + sample->pid =23 ; + +bpf_ringbuf_submit_dynptr (&ptr1,0 ); + +return 0 ; + +done: +bpf_ringbuf_discard_dynptr (&ptr2,0 ); +bpf_ringbuf_discard_dynptr (&ptr1,0 ); +return 0 ; +} +/* A data slice must be first checked for NULL */ SEC("?raw_tp")int data_slice_missing_null_check1 (void *ctx)
Signature · 1 line
2.30.2
Quoted 9 lines · Joanne Koong
When a data slice is obtained from a dynptr (through the
bpf_dynptr_dataAPI), the ref obj id of the dynptr must be found and then associated with the data slice.The ref obj id of the dynptr must be found *before* the caller saved regs are reset. Without this fix, the ref obj id tracking is not correct for dynptrs that are at an offset from the frame pointer.
Quoted 6 lines
Please also note that the data slice's ref obj id must be assigned after the ret types are parsed, since RET_PTR_TO_ALLOC_MEM-type return regs get zero-marked.
Fixes 34d4ef5775f776ec4b0d53a02d588bf3195cada6 ("bpf: Add dynptr data slices");Signed-off-by Joanne Koong <[email protected]>
merge conflict. pls respin.