From: Greg KH <greg@kroah.com>
To: Artem Dinaburg <artem@trailofbits.com>
Cc: stable@vger.kernel.org, Xiang Mei <xmei5@asu.edu>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 6.1.y] net: bonding: fix use-after-free in bond_xmit_broadcast()
Date: Thu, 20 Aug 2026 14:32:14 +0200 [thread overview]
Message-ID: <2026082028-curled-try-e7c5@gregkh> (raw)
In-Reply-To: <20260819165924.1184-1-artem@trailofbits.com>
On Wed, Aug 19, 2026 at 12:59:22PM -0400, Artem Dinaburg wrote:
> From: Xiang Mei <xmei5@asu.edu>
>
> Please queue the attached backport of upstream commit 2884bf72fb8f. It fixes
> CVE-2026-31419 in 6.1.y.
>
> An unprivileged user can create a broadcast bond and dummy slaves in a user
> and network namespace. Racing ordinary packet sends with slave release makes
> `bond_xmit_broadcast()` give the same skb to two transmitters. I reproduced a
> KASAN use-after-free in `skb_clone()` on v6.1.182.
>
> The attached one-line upstream fix applies cleanly to v6.1.182. The same
> workload completed over one million sends and 299 slave mutations with the
> patched module and no sanitizer, oops, lock, or BUG output.
>
> The fix is already released in 6.6.143, 6.12.95, 6.18.22, and 6.19.12, but no
> corresponding fix is present in 6.1.y.
>
> Signed-off-by: Artem Dinaburg <artem@trailofbits.com>
You stripped off all of the original commit changelog info :(
thanks,
greg k-h
prev parent reply other threads:[~2026-08-20 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:59 [PATCH 6.1.y] net: bonding: fix use-after-free in bond_xmit_broadcast() Artem Dinaburg
2026-08-20 12:32 ` Greg KH [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=2026082028-curled-try-e7c5@gregkh \
--to=greg@kroah.com \
--cc=artem@trailofbits.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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.