From: Jay Vosburgh <jv@jvosburgh.net>
To: Kota Toda <kota.toda@gmo-cybersecurity.com>
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yuki Koike <yuki.koike@gmo-cybersecurity.com>,
Jiayuan Chen <jiayuan.chen@linux.dev>
Subject: Re: [PATCH v4 0/2] net: bonding: fix type-confusion in bonding header_ops
Date: Thu, 05 Mar 2026 12:59:05 -0800 [thread overview]
Message-ID: <1356396.1772744345@famine> (raw)
In-Reply-To: <20260305110751.167489-1-kota.toda@gmo-cybersecurity.com>
Kota Toda <kota.toda@gmo-cybersecurity.com> wrote:
>In bond_setup_by_slave(), the slave’s header_ops are unconditionally
>copied into the bonding device. As a result, the bonding device may invoke
>the slave-specific header operations on itself, causing
>netdev_priv(bond_dev) (a struct bonding) to be incorrectly interpreted
>as the slave's private-data type.
>
>This type-confusion bug can lead to out-of-bounds writes into the skb,
>resulting in memory corruption.
A few days ago, Jiayuan Chen <jiayuan.chen@linux.dev> posted a
fix for what sounds like the same problem[0]. Their solution appears to
be much less complicated.
I also wonder how this bug was discovered. The code in question
hasn't changed in many years, and now there are two independent fixes
within a week.
[0] https://lore.kernel.org/netdev/20260228095854.391093-1-jiayuan.chen@linux.dev/
>Patch 1 stores the slave's header_ops in struct bonding and sets
>wrapper callbacks in bond_In bond_setup_by_slave(), the slave’s
>header_ops are unconditionally
>copied into the bonding device. As a result, the bonding device may invoke
>the slave-specific header operations on itself, causing
>netdev_priv(bond_dev) (a struct bonding) to be incorrectly interpreted
>as the slave's private-data type.
>
>Patch 2 uses READ_ONCE when loading header_ops callbacks
>to avoid races with concurrent updates.
With the READ_ONCE changes in a separate patch, does that mean
that patch 1 by itself is subject to race conditions that would result
in errors? If so, that's not acceptable, every patch must stand alone
and not break the kernel.
-J
>Fixes: 1284cd3a2b74 ("bonding: two small fixes for IPoIB support")
>Signed-off-by: Kota Toda <kota.toda@gmo-cybersecurity.com>
>Co-developed-by: Yuki Koike <yuki.koike@gmo-cybersecurity.com>
>Signed-off-by: Yuki Koike <yuki.koike@gmo-cybersecurity.com>
>
>Kota Toda (2):
> net: bonding: fix type-confusion in bonding header_ops
> net: add READ_ONCE for header_ops callbacks
>
> drivers/net/bonding/bond_main.c | 67 ++++++++++++++++++++++++++++++++-
> include/linux/netdevice.h | 41 ++++++++++++++------
> include/net/bonding.h | 5 +++
> include/net/cfg802154.h | 2 +-
> net/core/neighbour.c | 6 +--
> net/ipv4/arp.c | 2 +-
> net/ipv6/ndisc.c | 2 +-
> 7 files changed, 106 insertions(+), 19 deletions(-)
>
>--
>2.53.0
>
>
---
-Jay Vosburgh, jv@jvosburgh.net
next prev parent reply other threads:[~2026-03-05 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 11:07 [PATCH v4 0/2] net: bonding: fix type-confusion in bonding header_ops Kota Toda
2026-03-05 11:07 ` [PATCH v4 1/2] " Kota Toda
2026-03-05 11:07 ` [PATCH v4 2/2] net: read header_ops callbacks with READ_ONCE() Kota Toda
2026-03-05 20:59 ` Jay Vosburgh [this message]
2026-03-06 8:06 ` [PATCH v4 0/2] net: bonding: fix type-confusion in bonding header_ops Jiayuan Chen
2026-03-06 8:13 ` Jiayuan Chen
2026-03-10 10:45 ` 戸田晃太
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=1356396.1772744345@famine \
--to=jv@jvosburgh.net \
--cc=jeff@garzik.org \
--cc=jiayuan.chen@linux.dev \
--cc=kota.toda@gmo-cybersecurity.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yuki.koike@gmo-cybersecurity.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.