From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jiale Yao <yaojiale02@163.com>, Jiri Pirko <jiri@resnulli.us>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] team: reject ARPHRD_CAN devices in team_port_add
Date: Tue, 28 Jul 2026 09:11:39 +0200 [thread overview]
Message-ID: <b58d98e0-8fe3-4e4e-b8a5-c1c7e647ccca@hartkopp.net> (raw)
In-Reply-To: <20260723040032.2094322-1-yaojiale02@163.com>
On 23.07.26 06:00, Jiale Yao wrote:
> Enslaving a CAN device (e.g. vxcan) to a team master triggers a
> NULL pointer dereference in can_rx_unregister() inside
> net/can/af_can.c.
>
> During team_port_add(), the code only checks IFF_LOOPBACK but
> does not reject ARPHRD_CAN devices. After passing this gate,
> team_dev_type_check_change() calls team_setup_by_port() which
> sets dev->type = port_dev->type, adopting the CAN type for the
> team device. However, CAN devices operate on a fundamentally
> different Layer 2 architecture, relying on the CAN mid-layer
> private data structure (can_ml_priv) instead of standard
> Ethernet structures. Since the team driver never initializes
> can_ml_priv, subsequent CAN subsystem operations -- such as
> closing an ISOTP socket bound to the team interface via
> isotp_release() -- reach can_rx_unregister() which dereferences
> the NULL can_ml_priv, causing a kernel crash.
>
> The bonding driver already rejects CAN devices since commit
> 8ba68464e478 ("bonding: refuse to enslave CAN devices").
> Team, as a sibling aggregation path, needs the same protection.
>
> Fix this by adding an explicit ARPHRD_CAN check in
> team_port_add(), directly after the IFF_LOOPBACK guard,
> consistent with the approach taken in bond_enslave().
>
> Fixes: 1d76efe1577b ("team: add support for non-ethernet devices")
> Assisted-by: Claude:deepseek-v4-pro
> Signed-off-by: Jiale Yao <yaojiale02@163.com>
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
I did not know that the team driver had the same approach.
Thanks for catching this!
Best regards,
Oliver
> ---
> drivers/net/team/team_core.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/team/team_core.c b/drivers/net/team/team_core.c
> index feaa75fbf8fc..38f88a836010 100644
> --- a/drivers/net/team/team_core.c
> +++ b/drivers/net/team/team_core.c
> @@ -1224,6 +1224,13 @@ static int team_port_add(struct team *team, struct net_device *port_dev,
> return -EINVAL;
> }
>
> + if (port_dev->type == ARPHRD_CAN) {
> + NL_SET_ERR_MSG(extack, "CAN device can't be added as a team port");
> + netdev_err(dev, "Device %s is CAN device. CAN devices can't be added as a team port\n",
> + portname);
> + return -EINVAL;
> + }
> +
> if (netif_is_team_port(port_dev)) {
> NL_SET_ERR_MSG(extack, "Device is already a port of a team device");
> netdev_err(dev, "Device %s is already a port "
prev parent reply other threads:[~2026-07-28 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 4:00 [PATCH] team: reject ARPHRD_CAN devices in team_port_add Jiale Yao
2026-07-28 1:24 ` Jakub Kicinski
2026-07-28 5:18 ` jiale yao
2026-07-28 7:11 ` Oliver Hartkopp [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=b58d98e0-8fe3-4e4e-b8a5-c1c7e647ccca@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yaojiale02@163.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