From: Ido Schimmel <idosch@nvidia.com>
To: David Lee <david.lee@trailofbits.com>
Cc: dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
Kyle Zeng <kylebot@openai.com>,
Dominik 'Disconnect3d' Czarnota
<dominik.czarnota@trailofbits.com>,
Sven Eckelmann <sven@narfation.org>,
horms@kernel.org, YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] ipv6: prevent in6_dev_get() from resurrecting inet6_dev
Date: Tue, 4 Aug 2026 16:49:43 +0300 [thread overview]
Message-ID: <20260804134943.GA1121565@shredder> (raw)
In-Reply-To: <20260803122758.666112-1-david.lee@trailofbits.com>
On Mon, Aug 03, 2026 at 12:27:57PM +0000, David Lee wrote:
> From: Kyle Zeng <kylebot@openai.com>
>
> in6_dev_get() reads dev->ip6_ptr under RCU and then unconditionally
> increments its refcount. Device teardown can clear the pointer and drop
> the last reference between these operations. The increment then
> resurrects an object whose RCU free has already been queued, so callers
> can use it after it is freed.
>
> Use refcount_inc_not_zero() and return NULL when the object has already
> reached zero. RCU keeps the memory accessible through the attempted
> reference acquisition, and a successful increment pins the object for
> the caller.
>
> An independent run on the exact unpatched 6f5156d7a31a (v7.2-rc3)
> kernel reproduced the invalid reference acquisition as UID 1000:
>
> refcount_t: addition on 0; use-after-free.
> ip6_mc_source+0xef4/0x17e0
>
> It was followed by the corresponding reference underflow in
> ip6_mc_source(). The supplied trace from the same unpatched revision
> additionally shows the access after the RCU read-side section ends:
>
> BUG: KASAN: slab-use-after-free in mutex_lock+0x76/0xe0
> Write of size 8 at addr ffff888015b50240 by task poc/1219
>
> Bug found and triaged by OpenAI Security Research and
> validated by Trail of Bits.
>
> Fixes: 8814c4b53381 ("[IPV6] ADDRCONF: Convert addrconf_lock to RCU.")
> Cc: stable@vger.kernel.org
> Assisted-by: Codex:gpt-5.6-sol gpt-5.5-cyber
> Signed-off-by: Kyle Zeng <kylebot@openai.com>
> Co-developed-by: David Lee <david.lee@trailofbits.com>
> Signed-off-by: David Lee <david.lee@trailofbits.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2026-08-04 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:27 [PATCH net v2] ipv6: prevent in6_dev_get() from resurrecting inet6_dev David Lee
2026-08-04 13:49 ` Ido Schimmel [this message]
2026-08-04 22:30 ` patchwork-bot+netdevbpf
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=20260804134943.GA1121565@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=david.lee@trailofbits.com \
--cc=dominik.czarnota@trailofbits.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sven@narfation.org \
--cc=yoshfuji@linux-ipv6.org \
/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