* [PATCH net v5] net: qualcomm: rmnet: require CAP_NET_ADMIN in the real device netns for config ops
@ 2026-09-06 12:32 Abdifatah Suruur
2026-09-09 3:33 ` netdev-bot+sashiko
0 siblings, 1 reply; 2+ messages in thread
From: Abdifatah Suruur @ 2026-09-06 12:32 UTC (permalink / raw)
To: netdev, linux-kernel
Cc: subash.a.kasiviswanathan, sean.tranchetti, horms, stable,
Abdifatah Suruur
An rmnet device may be created with its real device in a different
netns than the rmnet device itself (rmnet_newlink() resolves it in
link_net), and the config paths below only check CAP_NET_ADMIN against
dev_net(dev), while mutating rmnet port state attached to the real
device:
- rmnet_changelink() rewrites the endpoint mux table and
port->data_format and, via rmnet_vnd_update_dev_mtu(), can shrink the
MTU of the rmnet endpoint netdevs.
- rmnet_add_bridge() and rmnet_del_bridge(), reachable via
ndo_add_slave/ndo_del_slave through RTM_SETLINK IFLA_MASTER, flip
port->rmnet_mode and port->bridge_ep on the real device's port; with
bridge_ep pointing at a caller-owned device, rmnet_rx_handler() then
forwards real-device ingress frames to it.
- rmnet_set_coalesce() rewrites the port aggregation parameters via
ETHTOOL_SCOALESCE (ioctl) or ETHTOOL_MSG_COALESCE_SET (netlink),
whose capability checks likewise only cover dev's netns.
A caller privileged only in the rmnet device's netns can therefore
rewrite the shared cellular data-path state owned by another netns, and
steer its ingress traffic.
Gate the rtnl paths with rtnl_dev_link_net_capable(), matching the
"require CAP_NET_ADMIN in the device netns for changelink" series
(vxlan/geneve, CVE-2026-68432), and gate the ethtool setter with
ns_capable() in the real device netns, mirroring the check dev_ethtool()
already applies to dev's netns. Report the new rejections through
extack where one is available.
Fixes: 2abb5792387e ("net: qualcomm: rmnet: Allow configuration updates to existing devices")
Fixes: 60d58f971c1077 ("net: qualcomm: rmnet: Implement bridge mode")
Cc: stable@vger.kernel.org
Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
---
v5:
- also gate rmnet_set_coalesce(), the ethtool setter that rewrites the
port aggregation parameters of the real device's port, per the
Sashiko review
- report the new capability rejections through extack where available
v4:
- use the netdev comment style, per Subash Abhinov Kasiviswanathan
v3:
- cover rmnet_add_bridge() and rmnet_del_bridge() with the same gate;
they mutate the same real-device port state via ndo_add_slave/
ndo_del_slave and have no capability check of their own
- correct the impact wording: rmnet_vnd_update_dev_mtu() only reads
real_dev->mtu; the MTU store lands on the rmnet endpoint netdevs via
rmnet_vnd_change_mtu(), not on the real device
v2:
- drop Reported-by: (implied for the author), per Jakub Kicinski
---
.../ethernet/qualcomm/rmnet/rmnet_config.c | 33 ++++++++++++++++++-
.../net/ethernet/qualcomm/rmnet/rmnet_vnd.c | 18 +++++++++-
2 files changed, 49 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
index bed6f63facf25..7757fcb2fcc9f 100644
--- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
+++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
@@ -312,6 +312,16 @@ static int rmnet_changelink(struct net_device *dev, struct nlattr *tb[],
if (!rmnet_is_real_dev_registered(real_dev))
return -ENODEV;
+ /* The rtnl path only checks CAP_NET_ADMIN against dev_net(dev),
+ * but the port state mutated below is attached to real_dev, which
+ * may live in a different netns.
+ */
+ if (!rtnl_dev_link_net_capable(dev, dev_net(real_dev))) {
+ NL_SET_ERR_MSG_MOD(extack,
+ "Changing the port settings requires CAP_NET_ADMIN in the real device network namespace");
+ return -EPERM;
+ }
+
port = rmnet_get_port_rtnl(real_dev);
if (data[IFLA_RMNET_MUX_ID]) {
@@ -441,6 +451,16 @@ 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(dev),
+ * but the port state mutated below is attached to real_dev, which
+ * may live in a different netns.
+ */
+ if (!rtnl_dev_link_net_capable(rmnet_dev, dev_net(real_dev))) {
+ NL_SET_ERR_MSG_MOD(extack,
+ "Attaching a bridge device requires CAP_NET_ADMIN in the real device network namespace");
+ return -EPERM;
+ }
+
port = rmnet_get_port_rtnl(real_dev);
/* If there is more than one rmnet dev attached, its probably being
@@ -489,7 +509,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(dev),
+ * but rmnet_unregister_bridge() below clears the bridge state of
+ * the real device's port, which may live in a different 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);
diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c b/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
index 4f0ddcedfa979..1f4a3246f254a 100644
--- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
+++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
@@ -4,9 +4,11 @@
* RMNET Data virtual network driver
*/
+#include <linux/capability.h>
#include <linux/etherdevice.h>
#include <linux/ethtool.h>
#include <linux/if_arp.h>
+#include <linux/netlink.h>
#include <net/pkt_sched.h>
#include "rmnet_config.h"
#include "rmnet_handlers.h"
@@ -240,9 +242,23 @@ static int rmnet_set_coalesce(struct net_device *dev,
struct netlink_ext_ack *extack)
{
struct rmnet_priv *priv = netdev_priv(dev);
+ struct net_device *real_dev = priv->real_dev;
struct rmnet_port *port;
- port = rmnet_get_port_rtnl(priv->real_dev);
+ /*
+ * The aggregation parameters live in the port attached to
+ * real_dev, which may reside in a different netns. The ethtool
+ * paths only require CAP_NET_ADMIN in dev's netns, so require it
+ * in real_dev's netns as well before mutating the shared port
+ * state.
+ */
+ if (!ns_capable(dev_net(real_dev)->user_ns, CAP_NET_ADMIN)) {
+ NL_SET_ERR_MSG_MOD(extack,
+ "Changing aggregation parameters requires CAP_NET_ADMIN in the real device network namespace");
+ return -EPERM;
+ }
+
+ port = rmnet_get_port_rtnl(real_dev);
if (kernel_coal->tx_aggr_max_frames < 1 || kernel_coal->tx_aggr_max_frames > 64)
return -EINVAL;
--
2.53.0
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH net v5] net: qualcomm: rmnet: require CAP_NET_ADMIN in the real device netns for config ops
2026-09-06 12:32 [PATCH net v5] net: qualcomm: rmnet: require CAP_NET_ADMIN in the real device netns for config ops Abdifatah Suruur
@ 2026-09-09 3:33 ` netdev-bot+sashiko
0 siblings, 0 replies; 2+ messages in thread
From: netdev-bot+sashiko @ 2026-09-09 3:33 UTC (permalink / raw)
To: suruurism
Cc: netdev, linux-kernel, subash.a.kasiviswanathan, sean.tranchetti,
horms, stable, kuba
Thank you for your contribution! Sashiko AI review found 2 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 1 · Low: 1
- [Medium] Wrong device passed to the netns gate on the ndo_del_slave
path.
- [Low] Missing Fixes: tag for the third fixed site.
--
net: qualcomm: rmnet: require CAP_NET_ADMIN in the real device netns for config ops
This adds capability checks in the real device's netns to three rmnet
config paths: rmnet_changelink() and the bridge add/del paths get
rtnl_dev_link_net_capable(), and rmnet_set_coalesce() gets an explicit
ns_capable() test. Rejections are reported through extack where one is
available.
A couple of questions below.
> Fixes: 2abb5792387e ("net: qualcomm: rmnet: Allow configuration updates to existing devices")
> Fixes: 60d58f971c1077 ("net: qualcomm: rmnet: Implement bridge mode")
> Cc: stable@vger.kernel.org
[Severity: Low]
The commit message enumerates three defective config paths, and the v5
changelog says the rmnet_set_coalesce() gate was added in this revision,
but only two Fixes: tags are present.
rmnet_set_coalesce() and the ETHTOOL_COALESCE_TX_AGGR interface it uses
came in with db8a563a9d9024 ("net: qualcomm: rmnet: add ethtool support
for configuring tx aggregation") in v6.3, so neither tag covers the
rmnet_vnd.c hunk.
With Cc: stable present, the oldest tag (60d58f971c1077, 2017) points
stable tooling at branches where rmnet_set_coalesce() does not exist and
the rmnet_vnd.c hunk cannot apply. Would it make sense to add:
Fixes: db8a563a9d9024 ("net: qualcomm: rmnet: add ethtool support for configuring tx aggregation")
> diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> index bed6f63facf25..7757fcb2fcc9f 100644
> --- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
> +++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c
[ ... ]
> @@ -441,6 +451,16 @@ 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(dev),
> + * but the port state mutated below is attached to real_dev, which
> + * may live in a different netns.
> + */
> + if (!rtnl_dev_link_net_capable(rmnet_dev, dev_net(real_dev))) {
> + NL_SET_ERR_MSG_MOD(extack,
> + "Attaching a bridge device requires CAP_NET_ADMIN in the real device network namespace");
> + return -EPERM;
> + }
> +
> port = rmnet_get_port_rtnl(real_dev);
>
> /* If there is more than one rmnet dev attached, its probably being
> @@ -489,7 +509,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(dev),
> + * but rmnet_unregister_bridge() below clears the bridge state of
> + * the real device's port, which may live in a different 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);
[Severity: Medium]
Should the first argument here be slave_dev rather than rmnet_dev?
rtnl_dev_link_net_capable() short-circuits when the device passed as dev
already lives in link_net:
net/core/rtnetlink.c:rtnl_dev_link_net_capable() {
return net_eq(link_net, dev_net(dev)) ||
ns_capable(link_net->user_ns, CAP_NET_ADMIN);
}
so the dev argument has to be the device whose netns the rtnl core
already required CAP_NET_ADMIN for. For ndo_add_slave/ndo_del_slave that
is the RTM_SETLINK target, i.e. slave_dev, not the master:
net/core/rtnetlink.c:do_set_master() {
struct net_device *upper_dev = netdev_master_upper_dev_get(dev);
...
err = ops->ndo_del_slave(upper_dev, dev);
...
upper_dev = __dev_get_by_index(dev_net(dev), ifindex);
...
err = ops->ndo_add_slave(upper_dev, dev, extack);
}
On the add path the master is re-resolved with
__dev_get_by_index(dev_net(dev), ifindex), so dev_net(rmnet_dev) equals
dev_net(slave_dev) and the two spellings happen to agree. On the del path
upper_dev comes from the existing adjacency with no netns re-check, so
rmnet_dev can be in a different netns than slave_dev.
If rmnet_dev sits in real_dev's netns while slave_dev lives elsewhere,
does net_eq(dev_net(rmnet_dev), dev_net(real_dev)) make the new gate pass
without checking any capability, even though the caller was only
authorized against dev_net(slave_dev)? rmnet_del_bridge() then goes on to
clear real_port->bridge_ep and real_port->rmnet_mode via
rmnet_unregister_bridge() and unregisters the slave port.
That topology looks constructible: rmnet_vnd_setup() does not set
netns_immutable, __dev_change_net_namespace() has no upper/lower device
restriction and preserves adjacencies, and rmnet_config_notify_cb() only
acts when rmnet_is_real_dev_registered(dev), so moving the rmnet device
into real_dev's netns leaves the master/slave link intact.
Passing slave_dev on both paths would keep the two sites consistent and
match what the core actually authorized.
> diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c b/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
> index 4f0ddcedfa979..1f4a3246f254a 100644
> --- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
> +++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
[ ... ]
> @@ -240,9 +242,23 @@ static int rmnet_set_coalesce(struct net_device *dev,
> + if (!ns_capable(dev_net(real_dev)->user_ns, CAP_NET_ADMIN)) {
> + NL_SET_ERR_MSG_MOD(extack,
> + "Changing aggregation parameters requires CAP_NET_ADMIN in the real device network namespace");
> + return -EPERM;
> + }
> +
> + port = rmnet_get_port_rtnl(real_dev);
This is the hunk referred to in the Fixes: tag question above.
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260906123212.10829-1-suruurism%40gmail.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-09 3:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-06 12:32 [PATCH net v5] net: qualcomm: rmnet: require CAP_NET_ADMIN in the real device netns for config ops Abdifatah Suruur
2026-09-09 3:33 ` netdev-bot+sashiko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox