From: Florian Westphal <fw@strlen.de>
To: Kyle Zeng <kylebot@openai.com>
Cc: netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
coreteam@netfilter.org, bridge@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
outbounddisclosures@openai.com
Subject: Re: [PATCH] netfilter: br_netfilter: reject unsafe neighbour devices for DNAT
Date: Sat, 7 Nov 2026 13:10:35 +0100 [thread overview]
Message-ID: <au8VOwNYrLAB7G7t@strlen.de> (raw)
In-Reply-To: <au79avuyDAz__s4t@com-75606>
Kyle Zeng <kylebot@openai.com> wrote:
> On Sat, Nov 07, 2026 at 08:25:41AM +0100, Florian Westphal wrote:
> > > + struct net_device *dev = neigh->dev;
> > > +
> > > + /* The neighbour queue must keep skb->dev alive. A VLAN
> > > + * device also holds a reference to its real device.
> > > + */
> > > + if (is_vlan_dev(dev))
> > > + dev = vlan_dev_real_dev(dev);
> > > + if (dev != skb->dev) {
> > > + neigh_release(neigh);
> > > + goto free_skb;
> > > + }
> > > +
[..]
>
> The VLAN check is intended to preserve existing VLAN DNAT behavior.
>
> bridge-nf-filter-vlan-tagged=1, bridge-nf-pass-vlan-input-dev=1, and br0.100, the earlier test can pass with
> dst->dev == dev == br0.100. The continuation then changes skb->dev to br0, so the strict comparison would
> drop that valid packet.
Then please consider sending a v2 that explains this.
/* The neighbour queue must keep skb->dev alive. dst->dev is either
* the bridge or a vlan on top of bridge
* (bridge-nf-pass-vlan-input-dev=1).
*/
might just be enough. Thanks.
prev parent reply other threads:[~2026-11-07 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 4:21 Kyle Zeng
2026-10-30 4:23 ` netdev-bot+sinfo
2026-10-31 18:50 ` Florian Westphal
2026-11-07 7:25 ` Florian Westphal
2026-11-07 10:28 ` Kyle Zeng
2026-11-07 12:10 ` Florian Westphal [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=au8VOwNYrLAB7G7t@strlen.de \
--to=fw@strlen.de \
--cc=bridge@lists.linux.dev \
--cc=coreteam@netfilter.org \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=outbounddisclosures@openai.com \
--cc=pablo@netfilter.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
all inboxes | Powered by JetHome®