From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,
syzbot+819eb928d120d2bdad0e@syzkaller.appspotmail.com,
Kuniyuki Iwashima <kuniyu@google.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] ipv6: anycast: insert aca into global hash under idev->lock
Date: Sat, 30 May 2026 13:00:13 +0800 [thread overview]
Message-ID: <63b950ee-a137-4c65-bace-915f813d5459@linux.dev> (raw)
In-Reply-To: <20260529135116.183e083e@kernel.org>
On 5/30/26 4:51 AM, Jakub Kicinski wrote:
> On Fri, 29 May 2026 23:22:18 +0800 Jiayuan Chen wrote:
>> syzbot reported a splat [1]: a slab-use-after-free in
>> ipv6_chk_acast_addr(), which walks the global inet6_acaddr_lst[] hash
>> under RCU and dereferences a struct ifacaddr6 that has already been
>> freed while still linked in the hash, so a later reader walks into a
>> dangling node.
> Please do not violate the 24h repost grace period on netdev.
> We are tracking the violations now, if you keep doing this
> there will be consequences..
Oops, sorry about that. I slept on it and somehow got confused about the
timing.
I will make sure to wait for the full 24 hours next time.
prev parent reply other threads:[~2026-05-30 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:22 [PATCH net v2] ipv6: anycast: insert aca into global hash under idev->lock Jiayuan Chen
2026-05-29 20:51 ` Jakub Kicinski
2026-05-30 5:00 ` Jiayuan Chen [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=63b950ee-a137-4c65-bace-915f813d5459@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+819eb928d120d2bdad0e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox