From: Qi Tang <tpluszz77@gmail.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
bpf@vger.kernel.org, Qi Tang <tpluszz77@gmail.com>
Subject: [PATCH] bpf: propagate ref_obj_id for dynptr slices of refcounted dynptrs
Date: Wed, 1 Apr 2026 01:26:19 +0800 [thread overview]
Message-ID: <20260331172619.29837-1-tpluszz77@gmail.com> (raw)
bpf_dynptr_slice() and bpf_dynptr_slice_rdwr() return PTR_TO_MEM
slices that carry only dynptr_id but not ref_obj_id. When a
refcounted dynptr (ringbuf, file) is released via submit or discard,
unmark_stack_slots_dynptr() invalidates state through
release_reference(ref_obj_id). Because the slice has no ref_obj_id,
it survives the release and remains usable as live PTR_TO_MEM.
This allows post-release reads and writes through the stale slice.
A BPF program can reserve a ringbuf dynptr, obtain a slice, submit
the dynptr, then continue writing through the slice into the
already-submitted ringbuf entry.
Set ref_obj_id on the returned slice register when the source dynptr
is refcounted, so release_reference() properly invalidates it.
The original comment stated "packet slices are not refcounted" which
was correct for the initial packet-only use case, but
bpf_dynptr_slice is a generic kfunc also used with refcounted ringbuf
and file dynptrs.
BPF verifier incorrectly accepts post-release slice access:
19: (85) call bpf_ringbuf_discard_dynptr ; dynptr released
20: (15) if r6 == 0x0 goto pc+6 ; R6=rdonly_mem(sz=64) ← stale
21: (71) r1 = *(u8 *)(r6 +0) ← reads freed memory
Fixes: 66e3a13e7c2c ("bpf: Add bpf_dynptr_slice and bpf_dynptr_slice_rdwr")
Signed-off-by: Qi Tang <tpluszz77@gmail.com>
---
kernel/bpf/verifier.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index f108c01ff6d0..937c9adf1b3d 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -14071,11 +14071,8 @@ static int check_special_kfunc(struct bpf_verifier_env *env, struct bpf_kfunc_ca
return -EFAULT;
}
regs[BPF_REG_0].dynptr_id = meta->initialized_dynptr.id;
-
- /* we don't need to set BPF_REG_0's ref obj id
- * because packet slices are not refcounted (see
- * dynptr_type_refcounted)
- */
+ if (dynptr_type_refcounted(meta->initialized_dynptr.type))
+ regs[BPF_REG_0].ref_obj_id = meta->initialized_dynptr.ref_obj_id;
} else {
return 0;
}
--
2.43.0
next reply other threads:[~2026-03-31 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 17:26 Qi Tang [this message]
2026-03-31 17:56 ` [PATCH] bpf: propagate ref_obj_id for dynptr slices of refcounted dynptrs Amery Hung
2026-04-01 2:06 ` Qi Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260331172619.29837-1-tpluszz77@gmail.com \
--to=tpluszz77@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox