From: <subash.a.kasiviswanathan@oss.qualcomm.com>
To: "'Jérémy Jean'" <Jeremy.Jean@oss.cyber.gouv.fr>,
"'Sean Tranchetti'" <sean.tranchetti@oss.qualcomm.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] net: qualcomm: rmnet: require real-netns admin for bridging
Date: Sat, 22 Aug 2026 15:27:32 -0600 [thread overview]
Message-ID: <000601dd327d$0b076e00$21164a00$@oss.qualcomm.com> (raw)
In-Reply-To: <20260821202845.4053530-2-Jeremy.Jean@oss.cyber.gouv.fr>
> -----Original Message-----
> From: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
> Sent: Friday, August 21, 2026 2:29 PM
> To: Subash Abhinov Kasiviswanathan
> <subash.a.kasiviswanathan@oss.qualcomm.com>; Sean Tranchetti
> <sean.tranchetti@oss.qualcomm.com>
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Jérémy Jean
> <Jeremy.Jean@oss.cyber.gouv.fr>
> Subject: [PATCH] net: qualcomm: rmnet: require real-netns admin for bridging
>
> An rmnet device remains linked to its real device after it is moved to a different
> network namespace. When it is used as a master, rmnet_add_bridge() follows
> that pointer and switches the real device's port to bridge mode.
>
> The rtnetlink master operation only requires CAP_NET_ADMIN in the
> namespace holding the visible rmnet and slave devices. A caller privileged only
> there can therefore bridge an attacker-controlled interface to the real device in
> another namespace, receiving and transmitting raw traffic across the
> namespace boundary.
>
> Require CAP_NET_ADMIN in the network namespace of the real device before
> configuring the bridge.
>
> Fixes: 60d58f971c10 ("net: qualcomm: rmnet: Implement bridge mode")
> Assisted-by: Codex:gpt-5
> Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
> ---
> drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> index bed6f63facf2..45e6c16a5a70 100644
> --- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> +++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> @@ -441,6 +441,14 @@ int rmnet_add_bridge(struct net_device
> *rmnet_dev,
> struct rmnet_port *port, *slave_port;
> int err;
>
> + /*
> + * The rtnl path only checks CAP_NET_ADMIN against
> dev_net(rmnet_dev),
> + * but bridge mode below controls real_dev, which may live in another
> + * netns.
> + */
> + if (!rtnl_dev_link_net_capable(rmnet_dev, dev_net(real_dev)))
> + return -EPERM;
> +
> port = rmnet_get_port_rtnl(real_dev);
>
> /* If there is more than one rmnet dev attached, its probably being
I believe the bridge tear down path might need a similar check. I've also added a minor update to account for the expected comment style.
diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
index bed6f63facf2..0f9734a40ed0 100644
--- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
+++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
@@ -441,6 +441,13 @@ int rmnet_add_bridge(struct net_device *rmnet_dev,
struct rmnet_port *port, *slave_port;
int err;
+ /* The rtnl path only checks CAP_NET_ADMIN against dev_net(rmnet_dev),
+ * but bridge mode below controls real_dev, which may live in another
+ * netns.
+ */
+ if (!rtnl_dev_link_net_capable(rmnet_dev, dev_net(real_dev)))
+ return -EPERM;
+
port = rmnet_get_port_rtnl(real_dev);
/* If there is more than one rmnet dev attached, its probably being
@@ -489,7 +496,19 @@ int rmnet_add_bridge(struct net_device *rmnet_dev,
int rmnet_del_bridge(struct net_device *rmnet_dev,
struct net_device *slave_dev)
{
- struct rmnet_port *port = rmnet_get_port_rtnl(slave_dev);
+ struct rmnet_priv *priv = netdev_priv(rmnet_dev);
+ struct net_device *real_dev = priv->real_dev;
+ struct rmnet_port *port;
+
+ /* Similar to rmnet_add_bridge(), the rtnl path only checks
+ * for CAP_NET_ADMIN against dev_net(slave_dev), but tearing
+ * down the bridge below updates the real_dev's port state,
+ * which may live in another netns.
+ */
+ if (!rtnl_dev_link_net_capable(rmnet_dev, dev_net(real_dev)))
+ return -EPERM;
+
+ port = rmnet_get_port_rtnl(slave_dev);
rmnet_unregister_bridge(port);
prev parent reply other threads:[~2026-08-22 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 20:28 Jérémy Jean
2026-08-22 21:27 ` subash.a.kasiviswanathan [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='000601dd327d$0b076e00$21164a00$@oss.qualcomm.com' \
--to=subash.a.kasiviswanathan@oss.qualcomm.com \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean.tranchetti@oss.qualcomm.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 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®