From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Florian Westphal <fw@strlen.de>, bpf@vger.kernel.org
Cc: andrii@kernel.org, eddyz87@gmail.com
Subject: Re: [PATCH v2 bpf] selftests/bpf: Add tests to assert that netfilter progs cannot write to skb
Date: Thu, 3 Sep 2026 18:27:53 +0800 [thread overview]
Message-ID: <0b318536-dcf8-48e0-ba9e-ae6dddcff80c@linux.dev> (raw)
In-Reply-To: <20260903065845.22762-1-fw@strlen.de>
on 9/3/26 2:58 PM, Florian Westphal wrote:
> The netfilter framework is allergic to ip header changing after
> validation done by ip/ipv6 stack.
>
> Assert that bpf netfilter programs do not allow skb write access.
>
> Following additional tests are expected to be rejected by verifier:
>
> 1. alter skb->len.
> 2. alter skb->data.
> 3. prog calls bpf_dynptr_slice_rdwr.
> 4. alter location returned by dynptr API.
>
> Add following test case for bpf runtime:
> - alter skb data via bpf_dynptr_write()
>
> Test checks via __retval() that bpf_dynptr_write() returned nonzero value.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Reviewed-by: Jiayuan Chen <jiayuan.chen@linux.dev>
> ---
> v2: follow LLM review: rename functions and clarify commit message.
>
> .../bpf/progs/verifier_netfilter_ctx.c | 78 +++++++++++++++++++
> 1 file changed, 78 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/progs/verifier_netfilter_ctx.c b/tools/testing/selftests/bpf/progs/verifier_netfilter_ctx.c
> index e2cbc5bda65e..b5d7f567d0d4 100644
> --- a/tools/testing/selftests/bpf/progs/verifier_netfilter_ctx.c
> +++ b/tools/testing/selftests/bpf/progs/verifier_netfilter_ctx.c
> @@ -113,4 +113,82 @@ int with_valid_ctx_access_test6(struct bpf_nf_ctx *ctx)
> return th->dest == bpf_htons(22) ? NF_ACCEPT : NF_DROP;
> }
>
> +SEC("netfilter")
> +__description("netfilter test prog with skb write access")
> +__failure __msg("only read is supported")
> +int skb_len_write(struct bpf_nf_ctx *ctx)
> +{
> + ctx->skb->len = 1;
> + return 1;
> +}
> +
> +SEC("netfilter")
> +__description("netfilter test prog with skb data write access")
> +__failure __msg("cannot write into rdonly_untrusted_mem")
> +int skb_data_write(struct bpf_nf_ctx *ctx)
> +{
> + ctx->skb->data[0] = 0;
> + return 1;
> +}
> +
> +SEC("netfilter")
> +__description("netfilter test prog with bpf_dynptr_write")
> +__success __failure_unpriv
> +__retval(0)
> +int with_dynptr_write(struct bpf_nf_ctx *ctx)
> +{
> + struct __sk_buff *skb = (struct __sk_buff *)ctx->skb;
> + struct bpf_dynptr ptr;
> + u8 buffer[1] = {};
> +
> + if (bpf_dynptr_from_skb(skb, 0, &ptr))
> + return 1;
> +
> + if (bpf_dynptr_write(&ptr, 0, buffer, sizeof(buffer), 0))
> + return 0; /* must always fail */
> +
> + return 1;
> +}
> +
> +SEC("netfilter")
> +__description("netfilter test prog with bpf_dynptr_slice_rdwr")
> +__failure __msg("the prog does not allow writes to packet data")
> +int with_dynptr_rdwr(struct bpf_nf_ctx *ctx)
> +{
> + struct __sk_buff *skb = (struct __sk_buff *)ctx->skb;
> + u8 buffer_iph[20] = {};
> + struct bpf_dynptr ptr;
> + struct iphdr *iph;
> +
> + if (bpf_dynptr_from_skb(skb, 0, &ptr))
> + return 1;
> +
> + iph = bpf_dynptr_slice_rdwr(&ptr, 0, buffer_iph, sizeof(buffer_iph));
> + if (!iph)
> + return 0;
> +
> + return 1;
> +}
> +
> +SEC("netfilter")
> +__description("netfilter test prog with bpf_dynptr_slice + write")
> +__failure __msg("cannot write into rdonly_mem")
> +int with_dynptr_store(struct bpf_nf_ctx *ctx)
> +{
> + struct __sk_buff *skb = (struct __sk_buff *)ctx->skb;
> + u8 buffer_iph[20] = {};
> + struct bpf_dynptr ptr;
> + struct iphdr *iph;
> +
> + if (bpf_dynptr_from_skb(skb, 0, &ptr))
> + return 1;
> +
> + iph = bpf_dynptr_slice(&ptr, 0, buffer_iph, sizeof(buffer_iph));
> + if (!iph)
> + return 0;
> + iph->protocol = 42;
> +
> + return 1;
> +}
> +
> char _license[] SEC("license") = "GPL";
next prev parent reply other threads:[~2026-09-03 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 6:58 [PATCH v2 bpf] selftests/bpf: Add tests to assert that netfilter progs cannot write to skb Florian Westphal
2026-09-03 10:27 ` Jiayuan Chen [this message]
2026-09-04 4:50 ` patchwork-bot+netdevbpf
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=0b318536-dcf8-48e0-ba9e-ae6dddcff80c@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=fw@strlen.de \
/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