Skip to content

Commit ef8fc7a

Browse files
kkdwivediAlexei Starovoitov
authored andcommitted
bpf: Fix partial dynptr stack slot reads/writes
Currently, while reads are disallowed for dynptr stack slots, writes are not. Reads don't work from both direct access and helpers, while writes do work in both cases, but have the effect of overwriting the slot_type. While this is fine, handling for a few edge cases is missing. Firstly, a user can overwrite the stack slots of dynptr partially. Consider the following layout: spi: [d][d][?] 2 1 0 First slot is at spi 2, second at spi 1. Now, do a write of 1 to 8 bytes for spi 1. This will essentially either write STACK_MISC for all slot_types or STACK_MISC and STACK_ZERO (in case of size < BPF_REG_SIZE partial write of zeroes). The end result is that slot is scrubbed. Now, the layout is: spi: [d][m][?] 2 1 0 Suppose if user initializes spi = 1 as dynptr. We get: spi: [d][d][d] 2 1 0 But this time, both spi 2 and spi 1 have first_slot = true. Now, when passing spi 2 to dynptr helper, it will consider it as initialized as it does not check whether second slot has first_slot == false. And spi 1 should already work as normal. This effectively replaced size + offset of first dynptr, hence allowing invalid OOB reads and writes. Make a few changes to protect against this: When writing to PTR_TO_STACK using BPF insns, when we touch spi of a STACK_DYNPTR type, mark both first and second slot (regardless of which slot we touch) as STACK_INVALID. Reads are already prevented. Second, prevent writing to stack memory from helpers if the range may contain any STACK_DYNPTR slots. Reads are already prevented. For helpers, we cannot allow it to destroy dynptrs from the writes as depending on arguments, helper may take uninit_mem and dynptr both at the same time. This would mean that helper may write to uninit_mem before it reads the dynptr, which would be bad. PTR_TO_MEM: [?????dd] Depending on the code inside the helper, it may end up overwriting the dynptr contents first and then read those as the dynptr argument. Verifier would only simulate destruction when it does byte by byte access simulation in check_helper_call for meta.access_size, and fail to catch this case, as it happens after argument checks. The same would need to be done for any other non-trivial objects created on the stack in the future, such as bpf_list_head on stack, or bpf_rb_root on stack. A common misunderstanding in the current code is that MEM_UNINIT means writes, but note that writes may also be performed even without MEM_UNINIT in case of helpers, in that case the code after handling meta && meta->raw_mode will complain when it sees STACK_DYNPTR. So that invalid read case also covers writes to potential STACK_DYNPTR slots. The only loophole was in case of meta->raw_mode which simulated writes through instructions which could overwrite them. A future series sequenced after this will focus on the clean up of helper access checks and bugs around that. Fixes: 97e03f5 ("bpf: Add verifier support for dynptrs") Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alexei Starovoitov <[email protected]>
1 parent 79168a6 commit ef8fc7a

File tree

2 files changed

+91
-3
lines changed

2 files changed

+91
-3
lines changed

kernel/bpf/verifier.c

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -769,6 +769,8 @@ static void mark_dynptr_cb_reg(struct bpf_reg_state *reg,
769769
__mark_dynptr_reg(reg, type, true);
770770
}
771771

772+
static int destroy_if_dynptr_stack_slot(struct bpf_verifier_env *env,
773+
struct bpf_func_state *state, int spi);
772774

773775
static int mark_stack_slots_dynptr(struct bpf_verifier_env *env, struct bpf_reg_state *reg,
774776
enum bpf_arg_type arg_type, int insn_idx)
@@ -863,6 +865,55 @@ static int unmark_stack_slots_dynptr(struct bpf_verifier_env *env, struct bpf_re
863865
return 0;
864866
}
865867

868+
static void __mark_reg_unknown(const struct bpf_verifier_env *env,
869+
struct bpf_reg_state *reg);
870+
871+
static int destroy_if_dynptr_stack_slot(struct bpf_verifier_env *env,
872+
struct bpf_func_state *state, int spi)
873+
{
874+
int i;
875+
876+
/* We always ensure that STACK_DYNPTR is never set partially,
877+
* hence just checking for slot_type[0] is enough. This is
878+
* different for STACK_SPILL, where it may be only set for
879+
* 1 byte, so code has to use is_spilled_reg.
880+
*/
881+
if (state->stack[spi].slot_type[0] != STACK_DYNPTR)
882+
return 0;
883+
884+
/* Reposition spi to first slot */
885+
if (!state->stack[spi].spilled_ptr.dynptr.first_slot)
886+
spi = spi + 1;
887+
888+
if (dynptr_type_refcounted(state->stack[spi].spilled_ptr.dynptr.type)) {
889+
verbose(env, "cannot overwrite referenced dynptr\n");
890+
return -EINVAL;
891+
}
892+
893+
mark_stack_slot_scratched(env, spi);
894+
mark_stack_slot_scratched(env, spi - 1);
895+
896+
/* Writing partially to one dynptr stack slot destroys both. */
897+
for (i = 0; i < BPF_REG_SIZE; i++) {
898+
state->stack[spi].slot_type[i] = STACK_INVALID;
899+
state->stack[spi - 1].slot_type[i] = STACK_INVALID;
900+
}
901+
902+
/* TODO: Invalidate any slices associated with this dynptr */
903+
904+
/* Do not release reference state, we are destroying dynptr on stack,
905+
* not using some helper to release it. Just reset register.
906+
*/
907+
__mark_reg_not_init(env, &state->stack[spi].spilled_ptr);
908+
__mark_reg_not_init(env, &state->stack[spi - 1].spilled_ptr);
909+
910+
/* Same reason as unmark_stack_slots_dynptr above */
911+
state->stack[spi].spilled_ptr.live |= REG_LIVE_WRITTEN;
912+
state->stack[spi - 1].spilled_ptr.live |= REG_LIVE_WRITTEN;
913+
914+
return 0;
915+
}
916+
866917
static bool is_dynptr_reg_valid_uninit(struct bpf_verifier_env *env, struct bpf_reg_state *reg)
867918
{
868919
struct bpf_func_state *state = func(env, reg);
@@ -3391,6 +3442,10 @@ static int check_stack_write_fixed_off(struct bpf_verifier_env *env,
33913442
env->insn_aux_data[insn_idx].sanitize_stack_spill = true;
33923443
}
33933444

3445+
err = destroy_if_dynptr_stack_slot(env, state, spi);
3446+
if (err)
3447+
return err;
3448+
33943449
mark_stack_slot_scratched(env, spi);
33953450
if (reg && !(off % BPF_REG_SIZE) && register_is_bounded(reg) &&
33963451
!register_is_null(reg) && env->bpf_capable) {
@@ -3504,6 +3559,14 @@ static int check_stack_write_var_off(struct bpf_verifier_env *env,
35043559
if (err)
35053560
return err;
35063561

3562+
for (i = min_off; i < max_off; i++) {
3563+
int spi;
3564+
3565+
spi = __get_spi(i);
3566+
err = destroy_if_dynptr_stack_slot(env, state, spi);
3567+
if (err)
3568+
return err;
3569+
}
35073570

35083571
/* Variable offset writes destroy any spilled pointers in range. */
35093572
for (i = min_off; i < max_off; i++) {
@@ -5531,6 +5594,31 @@ static int check_stack_range_initialized(
55315594
}
55325595

55335596
if (meta && meta->raw_mode) {
5597+
/* Ensure we won't be overwriting dynptrs when simulating byte
5598+
* by byte access in check_helper_call using meta.access_size.
5599+
* This would be a problem if we have a helper in the future
5600+
* which takes:
5601+
*
5602+
* helper(uninit_mem, len, dynptr)
5603+
*
5604+
* Now, uninint_mem may overlap with dynptr pointer. Hence, it
5605+
* may end up writing to dynptr itself when touching memory from
5606+
* arg 1. This can be relaxed on a case by case basis for known
5607+
* safe cases, but reject due to the possibilitiy of aliasing by
5608+
* default.
5609+
*/
5610+
for (i = min_off; i < max_off + access_size; i++) {
5611+
int stack_off = -i - 1;
5612+
5613+
spi = __get_spi(i);
5614+
/* raw_mode may write past allocated_stack */
5615+
if (state->allocated_stack <= stack_off)
5616+
continue;
5617+
if (state->stack[spi].slot_type[stack_off % BPF_REG_SIZE] == STACK_DYNPTR) {
5618+
verbose(env, "potential write to dynptr at off=%d disallowed\n", i);
5619+
return -EACCES;
5620+
}
5621+
}
55345622
meta->access_size = access_size;
55355623
meta->regno = regno;
55365624
return 0;

tools/testing/selftests/bpf/progs/dynptr_fail.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -420,7 +420,7 @@ int invalid_write1(void *ctx)
420420
* offset
421421
*/
422422
SEC("?raw_tp")
423-
__failure __msg("Expected an initialized dynptr as arg #3")
423+
__failure __msg("cannot overwrite referenced dynptr")
424424
int invalid_write2(void *ctx)
425425
{
426426
struct bpf_dynptr ptr;
@@ -444,7 +444,7 @@ int invalid_write2(void *ctx)
444444
* non-const offset
445445
*/
446446
SEC("?raw_tp")
447-
__failure __msg("Expected an initialized dynptr as arg #1")
447+
__failure __msg("cannot overwrite referenced dynptr")
448448
int invalid_write3(void *ctx)
449449
{
450450
struct bpf_dynptr ptr;
@@ -476,7 +476,7 @@ static int invalid_write4_callback(__u32 index, void *data)
476476
* be invalidated as a dynptr
477477
*/
478478
SEC("?raw_tp")
479-
__failure __msg("arg 1 is an unacquired reference")
479+
__failure __msg("cannot overwrite referenced dynptr")
480480
int invalid_write4(void *ctx)
481481
{
482482
struct bpf_dynptr ptr;

0 commit comments

Comments
 (0)