From: patchwork-bot+netdevbpf@kernel.org
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: jv@jvosburgh.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org,
syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.com
Subject: Re: [PATCH] bonding: refuse to enslave CAN devices
Date: Thu, 28 May 2026 00:10:04 +0000 [thread overview]
Message-ID: <177992700483.690389.17074233805341820738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260526-bonding-candev-v1-1-ba1df400918a@hartkopp.net>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 May 2026 21:33:19 +0200 you wrote:
> syzbot reported a kernel paging request crash in
> can_rx_unregister() inside net/can/af_can.c. The crash occurs
> because a virtual CAN device (vxcan) is being enslaved to a
> bonding master.
>
> During the enslavement process, the bonding driver mutates
> and modifies the network device states to fit an Ethernet-like
> aggregation model. However, CAN devices operate on a completely
> different Layer 2 architecture, relying on the CAN mid-layer
> private data structure (can_ml_priv) instead of standard
> Ethernet structures. Since bonding does not initialize or
> maintain these CAN structures, subsequent operations on the
> half-enslaved interface (such as closing associated sockets
> via isotp_release) lead to a null-pointer dereference when
> accessing the CAN receiver lists.
>
> [...]
Here is the summary with links:
- bonding: refuse to enslave CAN devices
https://git.kernel.org/netdev/net/c/8ba68464e478
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-05-28 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 19:33 [PATCH] bonding: refuse to enslave CAN devices Oliver Hartkopp
2026-05-27 1:36 ` Jay Vosburgh
2026-05-28 0:10 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 17:56 Oliver Hartkopp
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=177992700483.690389.17074233805341820738.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=socketcan@hartkopp.net \
--cc=syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.