From: Kuniyuki Iwashima <kuniyu@google.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@kernel.org>,
Harry Yoo <harry@kernel.org>
Cc: Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] mm/kasan: Detect double-free involving kfree_rcu_sheaf().
Date: Tue, 27 Oct 2026 06:15:15 +0000 [thread overview]
Message-ID: <auBA1_CNKLuO8Xus@google.com> (raw)
In-Reply-To: <20261009214639.2878857-1-kuniyu@google.com>
On Fri, 09 Oct 2026 21:46:24 +0000, Kuniyuki Iwashima wrote:
> Recently, syzbot has reported several weird use-after-free splats.
>
> What they have in common is that "Freed by" points to rcu_free_sheaf(),
> whereas the object shown in "Call Trace:" and "Allocated by" is never
> supposed to be freed via kfree_rcu().
>
> This means the object was a victim of a double-free somewhere else and
> was silently poisoned by rcu_free_sheaf() after being reallocated.
>
> This happens because kfree_rcu_sheaf() queues an object into the RCU
> sheaf without invoking any KASAN hooks.
>
> This series enables KASAN to detect double-free involving
> kfree_rcu_sheaf() immediately and adds KUnit tests for it.
Hi KASAN maintainers,
It would be appreciated if you review the series, or if
respin/repost would be preferred, please let me know.
Thank you !
prev parent reply other threads:[~2026-10-27 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 21:46 [PATCH 0/2] mm/kasan: Detect double-free involving kfree_rcu_sheaf() Kuniyuki Iwashima
2026-10-09 21:46 ` [PATCH 1/2] " Kuniyuki Iwashima
2026-10-20 12:29 ` Vlastimil Babka (SUSE)
2026-10-27 12:48 ` Alexander Potapenko
2026-10-27 21:51 ` Kuniyuki Iwashima
2026-10-09 21:46 ` [PATCH 2/2] mm/kasan/kunit: Add double-free tests " Kuniyuki Iwashima
2026-10-27 12:48 ` Alexander Potapenko
2026-10-27 22:16 ` Kuniyuki Iwashima
2026-10-27 6:15 ` Kuniyuki Iwashima [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=auBA1_CNKLuO8Xus@google.com \
--to=kuniyu@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cl@gentwo.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=vbabka@kernel.org \
--cc=vincenzo.frascino@arm.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