public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Jay Vosburgh <jv@jvosburgh.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Jiri Bohac <jbohac@suse.cz>,
	Liang Li <liali@redhat.com>,
	Nikolay Aleksandrov <nikolay@nvidia.com>
Subject: Re: [PATCHv2 net] bonding: alb: fix UAF in rlb_arp_recv during bond up/down
Date: Wed, 18 Feb 2026 04:36:24 +0000	[thread overview]
Message-ID: <aZVByEOAYdR3WF4q@fedora> (raw)
In-Reply-To: <20260217164355.7139ab53@kernel.org>

On Tue, Feb 17, 2026 at 04:43:55PM -0800, Jakub Kicinski wrote:
> On Sat, 14 Feb 2026 09:15:41 +0000 Hangbin Liu wrote:
> > Fixes: e53665c6eaa6 ("bonding: delete migrated IP addresses from the rlb hash table")
> 
> Ah, also AI says the issue existed already in 
> 3aba891dde38 ("bonding: move processing of recv handlers into
> handle_frame()")
> not the exact trapping instruction but the hash table was used from
> recv_probe so at least a UAF would happen.

Not sure if I understand correctly. Do you mean we still able to access
rlb_arp_recv() after setting recv_probe to NULL?

OK, that also count as UAF, even though not crash would happen.

Thanks
Hangbin

  reply	other threads:[~2026-02-18  4:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14  9:15 [PATCHv2 net] bonding: alb: fix UAF in rlb_arp_recv during bond up/down Hangbin Liu
2026-02-14 20:49 ` Jay Vosburgh
2026-02-18  0:42 ` Jakub Kicinski
2026-02-18  0:43 ` Jakub Kicinski
2026-02-18  4:36   ` Hangbin Liu [this message]
2026-02-19  0:11     ` Jakub Kicinski
2026-02-19 13:34       ` Hangbin Liu
2026-02-19 13:39         ` Hangbin Liu

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=aZVByEOAYdR3WF4q@fedora \
    --to=liuhangbin@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jbohac@suse.cz \
    --cc=jv@jvosburgh.net \
    --cc=kuba@kernel.org \
    --cc=liali@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=pabeni@redhat.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