linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Johan Hovold <johan@kernel.org>,
	syzbot <syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com>,
	Andrey Konovalov <andreyknvl@google.com>,
	dmg@turingmachine.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in adu_disconnect
Date: Fri, 20 Sep 2019 11:21:53 +0200	[thread overview]
Message-ID: <20190920092153.GN30545@localhost> (raw)
In-Reply-To: <CACT4Y+Yg5wTsMUGRmTwexKUMzi1ZxrH3k3yaMaJvLaEp7qnjSw@mail.gmail.com>

On Fri, Sep 20, 2019 at 11:13:14AM +0200, Dmitry Vyukov wrote:
> On Fri, Sep 20, 2019 at 11:08 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote:
> > > syzbot has found a reproducer for the following crash on:
> > >
> > > HEAD commit:    e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> > > git tree:       https://github.com/google/kasan.git usb-fuzzer
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=13871a4a600000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=cfa2c18fb6a8068e
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=0243cb250a51eeefb8cc
> > > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11c4c8e2600000
> > > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11d80d2c600000
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com
> > >
> > > usb 1-1: USB disconnect, device number 4
> > > ==================================================================
> > > BUG: KASAN: use-after-free in atomic64_read
> > > include/asm-generic/atomic-instrumented.h:836 [inline]
> > > BUG: KASAN: use-after-free in atomic_long_read
> > > include/asm-generic/atomic-long.h:28 [inline]
> > > BUG: KASAN: use-after-free in __mutex_unlock_slowpath+0x96/0x670
> > > kernel/locking/mutex.c:1211
> > > Read of size 8 at addr ffff8881d1d0aa00 by task kworker/0:1/12
> >
> > Let's resend and retest with commit id from latest report to make sure
> > the patch was actually applied during the last run:
> 
> The reply contains:
> patch:          https://syzkaller.appspot.com/x/patch.diff?x=1440268d600000
> that's what's being parsed and applied during testing.

Thanks for confirming, but I can't seem to find that link in the report
from syzbot:

	https://lkml.kernel.org/r/000000000000b05ce40592f8521a@google.com

Is it supposed to be there?

Johan

  reply	other threads:[~2019-09-20  9:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 11:58 KASAN: use-after-free Read in adu_disconnect syzbot
2019-08-09 20:24 ` syzbot
2019-09-19 10:35   ` Johan Hovold
2019-09-19 10:53     ` syzbot
2019-09-20  8:26     ` Johan Hovold
2019-09-20  9:02       ` syzbot
2019-09-20  9:08   ` Johan Hovold
2019-09-20  9:13     ` Dmitry Vyukov
2019-09-20  9:21       ` Johan Hovold [this message]
2019-09-20  9:28         ` Dmitry Vyukov
2019-09-20  9:35           ` Johan Hovold
2019-09-20 10:05             ` Dmitry Vyukov
2019-09-20  9:20     ` syzbot
2019-09-20 10:02       ` Johan Hovold
2019-09-20 10:08         ` Dmitry Vyukov
2019-09-20 10:16           ` Andrey Konovalov
2019-09-20 14:31           ` Johan Hovold
2019-09-20 10:21         ` syzbot
2019-09-20 14:38   ` Johan Hovold
2019-09-20 14:58     ` syzbot

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=20190920092153.GN30545@localhost \
    --to=johan@kernel.org \
    --cc=andreyknvl@google.com \
    --cc=dmg@turingmachine.org \
    --cc=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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).