From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Qian Cai <cai@lca.pw>
Cc: syzbot <syzbot+75867c44841cb6373570@syzkaller.appspotmail.com>,
Markus.Elfring@web.de, casey@schaufler-ca.com, dancol@google.com,
hdanton@sina.com, jmorris@namei.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stephen.smalley.work@gmail.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, yanfei.xu@windriver.com,
linux-next@vger.kernel.org
Subject: Re: KASAN: use-after-free Read in userfaultfd_release (2)
Date: Tue, 21 Jul 2020 14:32:33 +1000 [thread overview]
Message-ID: <20200721143233.23c89f2a@canb.auug.org.au> (raw)
In-Reply-To: <20200720155024.GC7354@lca.pw>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
Hi all,
On Mon, 20 Jul 2020 11:50:25 -0400 Qian Cai <cai@lca.pw> wrote:
>
> On Fri, Jul 17, 2020 at 11:05:41AM -0400, Qian Cai wrote:
> > On Mon, Jul 13, 2020 at 08:34:06AM -0700, syzbot wrote:
> > > syzbot has bisected this bug to:
> > >
> > > commit d08ac70b1e0dc71ac2315007bcc3efb283b2eae4
> > > Author: Daniel Colascione <dancol@google.com>
> > > Date: Wed Apr 1 21:39:03 2020 +0000
> > >
> > > Wire UFFD up to SELinux
> > >
> > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a79d13100000
> > > start commit: 89032636 Add linux-next specific files for 20200708
> > > git tree: linux-next
> > > final crash: https://syzkaller.appspot.com/x/report.txt?x=16a79d13100000
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=12a79d13100000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=64a250ebabc6c320
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=75867c44841cb6373570
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c4c8db100000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cbb68f100000
> > >
> > > Reported-by: syzbot+75867c44841cb6373570@syzkaller.appspotmail.com
> > > Fixes: d08ac70b1e0d ("Wire UFFD up to SELinux")
> > >
> > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> >
> > This is rather easy to reproduce here,
>
> James, Stephen, can you drop this patch? Daniel's email was bounced, and Viro
> mentioned the patch could be quite bad,
>
> https://lore.kernel.org/lkml/20200719165746.GJ2786714@ZenIV.linux.org.uk/
I have reverted that commit in linux-next today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-21 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 2:24 KASAN: use-after-free Read in userfaultfd_release (2) syzbot
2020-07-13 15:34 ` syzbot
2020-07-17 15:05 ` Qian Cai
2020-07-20 15:50 ` Qian Cai
2020-07-21 4:32 ` Stephen Rothwell [this message]
[not found] ` <20200713084512.10416-1-hdanton@sina.com>
2020-07-20 16:00 ` Al Viro
2020-07-20 23:46 ` Daniel Colascione
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=20200721143233.23c89f2a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Markus.Elfring@web.de \
--cc=cai@lca.pw \
--cc=casey@schaufler-ca.com \
--cc=dancol@google.com \
--cc=hdanton@sina.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=syzbot+75867c44841cb6373570@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yanfei.xu@windriver.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).