From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: subash.a.kasiviswanathan@oss.qualcomm.com
Cc: 'Sean Tranchetti' <sean.tranchetti@oss.qualcomm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: qualcomm: rmnet: require real-netns admin for bridging
Date: Mon, 05 Oct 2026 10:16:14 +0200 [thread overview]
Message-ID: <3350a4902b5da1e5315206d26513019b@oss.cyber.gouv.fr> (raw)
In-Reply-To: <000a01dd548c$ea3417a0$be9c46e0$@oss.qualcomm.com>
On 2026-10-05 07:46, subash.a.kasiviswanathan@oss.qualcomm.com wrote:
>> -----Original Message-----
>> From: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
>> Sent: Sunday, October 4, 2026 2:32 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>; stable@vger.kernel.org
>> Subject: [PATCH net v2] net: qualcomm: rmnet: require real-netns admin
>> for
>> bridging
>>
>> An rmnet device keeps its link to the real device when moved to
>> another
>> network namespace. The bridge callbacks change the real port, but
>> rtnetlink
>> only checks CAP_NET_ADMIN in the slave device's namespace.
>>
>> Require CAP_NET_ADMIN in the real device's namespace before adding or
>> removing a bridge. Use the slave device's namespace for the
>> comparison, since
>> that is the namespace rtnetlink authorized.
>>
>> Fixes: 60d58f971c10 ("net: qualcomm: rmnet: Implement bridge mode")
>> Cc: stable@vger.kernel.org
>> Assisted-by: LLM
>> Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
>> ---
>>
>> Changes in v2, after Subash Abhinov's review:
>> - Add the teardown check and use slave_dev for both capability checks.
>>
>> v1: https://lore.kernel.org/all/20260821202845.4053530-2-
>> Jeremy.Jean@oss.cyber.gouv.fr/
>>
>> .../ethernet/qualcomm/rmnet/rmnet_config.c | 20
>> ++++++++++++++++++-
>> 1 file changed, 19 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
>> b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
>> index bed6f63facf2..62d7acb13e0c 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(slave_dev),
>> + * but bridge mode below controls real_dev, which may live in
>> another
>> + * netns.
>> + */
>> + if (!rtnl_dev_link_net_capable(slave_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,18 @@ 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;
>> +
>> + /* The rtnl path only checks CAP_NET_ADMIN against
>> dev_net(slave_dev),
>> + * but bridge teardown also updates real_dev, which may live in
>> another
>> + * netns.
>> + */
>> + if (!rtnl_dev_link_net_capable(slave_dev, dev_net(real_dev)))
>> + return -EPERM;
>> +
>> + port = rmnet_get_port_rtnl(slave_dev);
>>
>> rmnet_unregister_bridge(port);
>>
>
> A similar patch was committed recently in net-next. Please refer to
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=26ee8cd69d46a14b37ba5e512084fe80d730127a
Thanks for the pointer.
I was too slow processing your feedbacks, but good that it is patched.
Regards,
Jérémy
next prev parent reply other threads:[~2026-10-05 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 20:31 [PATCH net v2] net: qualcomm: rmnet: require real-netns admin for bridging Jérémy Jean
2026-10-04 20:33 ` netdev-bot+sinfo
2026-10-05 5:46 ` subash.a.kasiviswanathan
2026-10-05 8:16 ` Jérémy Jean [this message]
2026-10-05 21:06 ` netdev-bot+sashiko
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=3350a4902b5da1e5315206d26513019b@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean.tranchetti@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=subash.a.kasiviswanathan@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