From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf-next v1 0/2] Fix for untrusted BTF pointer writes
Date: Tue, 7 Jul 2026 21:02:11 +0200 [thread overview]
Message-ID: <20260707190214.1997705-1-memxor@gmail.com> (raw)
When using custom btf_struct_access() callbacks, we miss rejecting
unstrusted BTF pointer writes. Fix and add a selftest for coverage.
Kumar Kartikeya Dwivedi (1):
selftests/bpf: Add untrusted BTF write regression
Nicholas Dudar (1):
bpf: Reject writes through untrusted BTF pointers
kernel/bpf/verifier.c | 8 ++++--
.../selftests/bpf/prog_tests/bpf_tcp_ca.c | 12 +++++++++
.../bpf/progs/tcp_ca_untrusted_btf_write.c | 26 +++++++++++++++++++
3 files changed, 44 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/tcp_ca_untrusted_btf_write.c
base-commit: f425a0443b7f0221a4b34f6acc0c2924bf5877f2
--
2.53.0
next reply other threads:[~2026-07-07 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 19:02 Kumar Kartikeya Dwivedi [this message]
2026-07-07 19:02 ` [PATCH bpf-next v1 1/2] bpf: Reject writes through untrusted BTF pointers Kumar Kartikeya Dwivedi
2026-07-07 19:48 ` bot+bpf-ci
2026-07-07 22:10 ` Amery Hung
2026-07-07 19:02 ` [PATCH bpf-next v1 2/2] selftests/bpf: Add untrusted BTF write regression Kumar Kartikeya Dwivedi
2026-07-07 22:31 ` Amery Hung
2026-07-07 22:36 ` Kumar Kartikeya Dwivedi
2026-07-07 22:58 ` Amery Hung
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=20260707190214.1997705-1-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.