From: Jason Gunthorpe <jgg@ziepe.ca>
To: Hao Sun <sunhao.th@gmail.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org, leon@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: KASAN: use-after-free Read in cma_cancel_operation, rdma_listen
Date: Tue, 13 Apr 2021 10:44:58 -0300 [thread overview]
Message-ID: <20210413134458.GI227011@ziepe.ca> (raw)
In-Reply-To: <CACkBjsb2QU3+J3mhOT2nb0YRB0XodzKoNTwF3RCufFbSoXNm6A@mail.gmail.com>
On Tue, Apr 13, 2021 at 09:42:43PM +0800, Hao Sun wrote:
> Jason Gunthorpe <jgg@ziepe.ca> 于2021年4月13日周二 下午9:34写道：
> >
> > On Tue, Apr 13, 2021 at 11:36:41AM +0800, Hao Sun wrote:
> > > Hi
> > >
> > > When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
> > > the Linux kernel, I found two use-after-free bugs which have been
> > > reported a long time ago by Syzbot.
> > > Although the corresponding patches have been merged into upstream,
> > > these two bugs can still be triggered easily.
> > > The original information about Syzbot report can be found here:
> > > https://syzkaller.appspot.com/bug?id=8dc0bcd9dd6ec915ba10b3354740eb420884acaa
> > > https://syzkaller.appspot.com/bug?id=95f89b8fb9fdc42e28ad586e657fea074e4e719b
> >
> > Then why hasn't syzbot seen this in a year's time? Seems strange
> >
>
> Seems strange to me too, but the fact is that the reproduction program
> in attachment can trigger these two bugs quickly.
Do you have this in the C format?
Jason
next prev parent reply other threads:[~2021-04-13 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 3:36 KASAN: use-after-free Read in cma_cancel_operation, rdma_listen Hao Sun
2021-04-13 13:33 ` Jason Gunthorpe
2021-04-13 13:42 ` Hao Sun
2021-04-13 13:44 ` Jason Gunthorpe [this message]
2021-04-13 14:09 ` Haakon Bugge
2021-04-13 14:19 ` Hao Sun
2021-04-19 17:50 ` Jason Gunthorpe
2021-09-16 18:35 ` Jason Gunthorpe
2021-09-17 1:01 ` Hao Sun
2021-09-17 2:03 ` Hao Sun
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=20210413134458.GI227011@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sunhao.th@gmail.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;
as well as URLs for NNTP newsgroup(s).