summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorEduard Zingerman <eddyz87@gmail.com>2026-08-27 15:48:23 -0700
committerAlexei Starovoitov <ast@kernel.org>2026-08-28 10:44:21 -0700
commit2f3536bff8823d3c5fdbbe15e17bfca696cc2b2e (patch)
tree919ab88efc8d300ff2a6ba8d56111ab530916256 /scripts
parentce6dcd0aed185432d02cafc82b738318af257ccd (diff)
downloadlinux-2f3536bff8823d3c5fdbbe15e17bfca696cc2b2e.tar.gz
linux-2f3536bff8823d3c5fdbbe15e17bfca696cc2b2e.zip
bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO
states.c:__clean_func_state() can downgrade scalar zero spill to STACK_ZERO in the following case: *(u64 *)(r10 - 8) = 0; ... checkpoint ... r1 = *(u32 *)(r10 - 4); ... no reads from r10-8 ... Here 4 bytes at r10-8 are dead and verifier changes scalar spill to a combination: 0000pppp (p stands for poison). Such a change breaks precision propagation chains. All places that produce STACK_ZERO should call bpf_mark_chain_precision() for the zero source. This patch fixes the bug in a simplest way possible: avoids converting stack spills of zero to STACK_ZERO. Two smarter approaches are possible: - do bpf_mark_chain_precision() from __clean_func_state() - check slot liveness information in check_stack_write_fixed_off() I investigated both and the changes required are a bit tricky, hence go with a simple fix for the time being. Fixes: be23266b4a08 ("bpf: 4-byte precise clean_verifier_state") Reported-by: Nicholas Carlini <npc@anthropic.com> Suggested-by: Nicholas Carlini <npc@anthropic.com> Signed-off-by: Eduard Zingerman <eddyz87@gmail.com> Link: https://lore.kernel.org/r/20260827-bug-011-cleanfunc-stack-zero-simple-v1-v1-1-c0e996589a52@gmail.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions