All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	"Ricardo Cañuelo Navarro" <rcn@igalia.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"David S. Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [RFC] Use after free in BPF/ XDP during XDP_REDIRECT
Date: Mon, 17 Mar 2025 11:29:43 +0100	[thread overview]
Message-ID: <874izshrvs.fsf@toke.dk> (raw)
In-Reply-To: <20250314172749.hsmtyM3N@linutronix.de>

Sebastian Andrzej Siewior <bigeasy@linutronix.de> writes:

> On 2025-03-14 17:03:35 [+0100], Toke Høiland-Jørgensen wrote:
>> > While at it, is there anything that ensures that only bpf_prog_run_xdp()
>> > can invoke the map_redirect callback? Mainline only assigns the task
>> > pointer in NAPI callback so any usage outside of bpf_prog_run_xdp() will
>> > lead to a segfault and I haven't seen a report yet so…
>> 
>> Yes, the verifier restricts which program types can call the
>> map_redirect helper.
>
> Okay. So checks for the BPF_PROG_TYPE_XDP type for the map_redirect and
> that is the only one setting it. Okay. Now I remember Alexei mentioning
> something…

Yeah, there's basically a mapping between BPF program types and the
available helpers. For XDP this is in xdp_func_proto() in net/core/filter.c.

>> > --- a/include/net/xdp.h
>> > +++ b/include/net/xdp.h
>> > @@ -486,7 +486,12 @@ static __always_inline u32 bpf_prog_run_xdp(const struct bpf_prog *prog,
>> >  	 * under local_bh_disable(), which provides the needed RCU protection
>> >  	 * for accessing map entries.
>> >  	 */
>> > -	u32 act = __bpf_prog_run(prog, xdp, BPF_DISPATCHER_FUNC(xdp));
>> > +	struct bpf_redirect_info *ri = this_cpu_ptr(&bpf_redirect_info);
>> > +	u32 act;
>> > +
>> 
>> Add an if here like
>> 
>> if (ri->map_id | ri->map_type) { /* single | to make it a single branch */
>> 
>> > +	ri->map_id = INT_MAX;
>> > +	ri->map_type = BPF_MAP_TYPE_UNSPEC;
>> 
>> }
>> 
>> Also, ri->map_id should be set to 0, not INT_MAX.
>
> The or variant does
>
> |         add %gs:this_cpu_off(%rip), %rax        # this_cpu_off, tcp_ptr__
> |         movl    32(%rax), %edx  # _51->map_id, _51->map_id
> |         orl     36(%rax), %edx  # _51->map_type, tmp311
> |         je      .L1546  #,
> |         movq    $0, 32(%rax)    #, MEM <vector(2) unsigned int> [(unsigned int *)_51 + 32B]
> | .L1546:
>
> while the || does
>
> |         add %gs:this_cpu_off(%rip), %rax        # this_cpu_off, tcp_ptr__
> |         cmpq    $0, 32(%rax)    #, *_51
> |         je      .L1546  #,
> |         movq    $0, 32(%rax)    #, MEM <vector(2) unsigned int> [(unsigned int *)_51 + 32B]
> | .L1546:
>
> gcc isn't bad at optimizing here ;)

Ohh, neat! Didn't consider that this is two U32s, so they can be loaded
in one go. That's what I get from trying to second-guess the compiler, I
suppose :)

Let's just go with the obvious one (||) instead of the OR thing, then.

> This is the or version as asked for. I don't mind doing any of the both.
> I everyone agrees then I would send it to Greg.

Sure, with the above, feel free to add my:

Acked-by: Toke Høiland-Jørgensen <toke@kernel.org>

  reply	other threads:[~2025-03-17 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 18:39 [RFC] Use after free in BPF/ XDP during XDP_REDIRECT Sebastian Andrzej Siewior
2025-03-13 19:28 ` Toke Høiland-Jørgensen
2025-03-13 20:32   ` Sebastian Andrzej Siewior
2025-03-14  9:21     ` Toke Høiland-Jørgensen
2025-03-14 15:30       ` Sebastian Andrzej Siewior
2025-03-14 16:03         ` Toke Høiland-Jørgensen
2025-03-14 17:27           ` Sebastian Andrzej Siewior
2025-03-17 10:29             ` Toke Høiland-Jørgensen [this message]
2025-03-17 12:01               ` Ricardo Cañuelo Navarro

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=874izshrvs.fsf@toke.dk \
    --to=toke@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rcn@igalia.com \
    --cc=tglx@linutronix.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 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.