From: Jason Gunthorpe <jgg@ziepe.ca>
To: Will Deacon <will@kernel.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
syzbot <syzbot+90c2d711b5218d10ce61@syzkaller.appspotmail.com>,
baolu.lu@linux.intel.com, dwmw2@infradead.org,
iommu@lists.linux.dev, joro@8bytes.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iommu?] KASAN: slab-use-after-free Read in free_iova
Date: Tue, 11 Aug 2026 10:49:53 -0300 [thread overview]
Message-ID: <20260811134953.GB544626@ziepe.ca> (raw)
In-Reply-To: <anrv1SUHgtx_ELb8@willie-the-truck>
On Tue, Aug 11, 2026 at 10:48:05AM +0100, Will Deacon wrote:
> On Mon, Aug 10, 2026 at 02:32:30PM -0300, Jason Gunthorpe wrote:
> > On Mon, Aug 10, 2026 at 11:50:28AM +0100, Robin Murphy wrote:
> > > > Freed by task 5327:
> > > > kasan_save_stack mm/kasan/common.c:57 [inline]
> > > > kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
> > > > kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:584
> > > > poison_slab_object mm/kasan/common.c:253 [inline]
> > > > __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:285
> > > > kasan_slab_free include/linux/kasan.h:235 [inline]
> > > > slab_free_hook mm/slub.c:2677 [inline]
> > > > slab_free mm/slub.c:6377 [inline]
> > > > kmem_cache_free+0x182/0x650 mm/slub.c:6504
> > > > free_iova_mem drivers/iommu/iova.c:237 [inline]
> > > > put_iova_domain+0xcc/0x100 drivers/iommu/iova.c:454
> > >
> > > ...except that right in between here we've called iommu_dma_free_fq() which
> > > would have already invoked timer_delete_sync() and freed the queue itself.
> > > Wut?
> >
> > I've been feeding syzkaller riddles to the best AI I can get and it is
> > surprisingly good.. So, for this it guesses:
>
> Huh, that's a pretty good idea. Do you just dunk the report in verbatim,
> or do you have a cleverly crafted prompt that you're having more success
> with?
I usually take the email into a file, download any reproducer and just
feed it to it. 'Here is a bug description in xyz.txt what could be
wrong' and play the lottery. On this one it could understand the http
links and it fetched down the console logs and other information from
the dashboard on its own (This was GPT Sol 5.6)
Even if it isn't right out of the gate it is usually still interesting
and points at new things to think about
Like this theory about concurrent unmap is a good guess, but there is
a big gap between that guess and finding the source of the unmap.
Jason
next prev parent reply other threads:[~2026-08-11 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 23:44 [syzbot] [iommu?] KASAN: slab-use-after-free Read in free_iova syzbot
2026-08-10 10:50 ` Robin Murphy
2026-08-10 17:32 ` Jason Gunthorpe
2026-08-11 9:48 ` Will Deacon
2026-08-11 13:49 ` Jason Gunthorpe [this message]
2026-08-11 12:57 ` Robin Murphy
2026-08-11 13:11 ` Jason Gunthorpe
2026-08-13 16:59 ` Robin Murphy
2026-08-13 17:09 ` Jason Gunthorpe
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=20260811134953.GB544626@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=syzbot+90c2d711b5218d10ce61@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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 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.