public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Kohei Enju <kohei@enjuk.jp>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	Alexei Starovoitov <ast@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>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Jussi Maki <joamaki@gmail.com>,
	kohei.enju@gmail.com,
	syzbot+10cc7f13760b31bd2e61@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 bpf] bpf: devmap: fix stack-out-of-bounds write in get_upper_ifindexes()
Date: Mon, 23 Feb 2026 22:32:38 +0900	[thread overview]
Message-ID: <aZxVELsXHvrpkicA@x1> (raw)
In-Reply-To: <87ikbnofug.fsf@toke.dk>

On 02/23 12:32, Toke Høiland-Jørgensen wrote:
> Kohei Enju <kohei@enjuk.jp> writes:
> 
> > get_upper_ifindexes() iterates over all upper devices and writes their
> > indices into an array without checking bounds.
> >
> > Also the callers assume that the max number of upper devices is
> > MAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack,
> > but that assumption is not correct and the number of upper devices could
> > be larger than MAX_NEST_DEV (e.g., many macvlans), causing a
> > stack-out-of-bounds write.
> >
> > Add a max parameter to get_upper_ifindexes() to avoid the issue.
> >
> > To reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with
> > an XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS.
> > Then send a packet to the device to trigger the XDP redirect path.
> >
> > Reported-by: syzbot+10cc7f13760b31bd2e61@syzkaller.appspotmail.com
> > Closes: https://lore.kernel.org/all/698c4ce3.050a0220.340abe.000b.GAE@google.com/T/
> > Fixes: aeea1b86f936 ("bpf, devmap: Exclude XDP broadcast to master device")
> > Signed-off-by: Kohei Enju <kohei@enjuk.jp>
> > ---
> > Changes:
> >   v2:
> >     - fix formatting, accounting that max-line-length is 100
> >   v1: https://lore.kernel.org/bpf/20260216201428.65641-1-kohei@enjuk.jp/
> > ---
> >  kernel/bpf/devmap.c | 12 ++++++++----
> >  1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/kernel/bpf/devmap.c b/kernel/bpf/devmap.c
> > index 2625601de76e..c8c49d86a403 100644
> > --- a/kernel/bpf/devmap.c
> > +++ b/kernel/bpf/devmap.c
> > @@ -588,16 +588,18 @@ static inline bool is_ifindex_excluded(int *excluded, int num_excluded, int ifin
> >  }
> >  
> >  /* Get ifindex of each upper device. 'indexes' must be able to hold at
> > - * least MAX_NEST_DEV elements.
> > + * least 'max' elements.
> >   * Returns the number of ifindexes added.
> >   */
> > -static int get_upper_ifindexes(struct net_device *dev, int *indexes)

> > +static int get_upper_ifindexes(struct net_device *dev, int *indexes, int max)
> >  {
> >  	struct net_device *upper;
> >  	struct list_head *iter;
> >  	int n = 0;
> >  
> >  	netdev_for_each_upper_dev_rcu(dev, upper, iter) {
> > +		if (n >= max)
> > +			break;
> 
> Hmm, how about returning an error here, and aborting the redirect
> entirely? This silent truncation to an arbitrary number seems a bit
> surprising, and very hard to debug. With an error, there will at least
> be an error tracepoint to catch the failure.
> 
> -Toke

Hi, Toke. 

Thanks for the review.
Indeed I agree that silent truncation is surprising and hard to debug.
I'll send a v3 that returns -EOVERFLOW and aborts the redirect when
there are too many upper devices.

      reply	other threads:[~2026-02-23 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 19:29 [PATCH v2 bpf] bpf: devmap: fix stack-out-of-bounds write in get_upper_ifindexes() Kohei Enju
2026-02-23 11:32 ` Toke Høiland-Jørgensen
2026-02-23 13:32   ` Kohei Enju [this message]

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=aZxVELsXHvrpkicA@x1 \
    --to=kohei@enjuk.jp \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=joamaki@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kohei.enju@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=syzbot+10cc7f13760b31bd2e61@syzkaller.appspotmail.com \
    --cc=toke@redhat.com \
    --cc=yonghong.song@linux.dev \
    /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