From: Johan Hovold <johan@kernel.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: syzbot <syzbot+7c72edfb407b2bd866ce@syzkaller.appspotmail.com>,
amitkarwar@gmail.com, "David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-wireless@vger.kernel.org, netdev <netdev@vger.kernel.org>,
siva8118@gmail.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: invalid-free in rsi_91x_deinit
Date: Thu, 28 Nov 2019 18:09:27 +0100 [thread overview]
Message-ID: <20191128170927.GB29518@localhost> (raw)
In-Reply-To: <20191128170702.GA29518@localhost>
On Thu, Nov 28, 2019 at 06:07:02PM +0100, Johan Hovold wrote:
> On Tue, Nov 19, 2019 at 02:38:11PM +0100, Andrey Konovalov wrote:
> > On Tue, Apr 23, 2019 at 2:36 PM syzbot
> > <syzbot+7c72edfb407b2bd866ce@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: d34f9519 usb-fuzzer: main usb gadget fuzzer driver
> > > git tree: https://github.com/google/kasan/tree/usb-fuzzer
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=14a79403200000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=c73d1bb5aeaeae20
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=7c72edfb407b2bd866ce
> > > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17547247200000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147b3a1d200000
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+7c72edfb407b2bd866ce@syzkaller.appspotmail.com
> > >
> > > usb 1-1: config 252 interface 115 altsetting 0 has 1 endpoint descriptor,
> > > different from the interface descriptor's value: 4
> > > usb 1-1: New USB device found, idVendor=1618, idProduct=9113,
> > > bcdDevice=32.21
> > > usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > rsi_91x: rsi_probe: Failed to init usb interface
> > > ==================================================================
> > > BUG: KASAN: double-free or invalid-free in slab_free mm/slub.c:3003 [inline]
> > > BUG: KASAN: double-free or invalid-free in kfree+0xce/0x280 mm/slub.c:3958
> > Most likely the same issue as:
> >
> > #syz dup: WARNING: ODEBUG bug in rsi_probe
> >
> > https://syzkaller.appspot.com/bug?extid=1d1597a5aa3679c65b9f
>
> No, this was separate bug that was fixed by commit 8b51dc729147 ("rsi:
> fix a double free bug in rsi_91x_deinit()").
>
> Let me try to mark it as such:
>
> #syz undup
#syz fix: rsi: fix a double free bug in rsi_91x_deinit()
Johan
prev parent reply other threads:[~2019-11-28 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 12:36 KASAN: invalid-free in rsi_91x_deinit syzbot
2019-11-19 13:38 ` Andrey Konovalov
2019-11-28 17:07 ` Johan Hovold
2019-11-28 17:09 ` Johan Hovold [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=20191128170927.GB29518@localhost \
--to=johan@kernel.org \
--cc=amitkarwar@gmail.com \
--cc=andreyknvl@google.com \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=siva8118@gmail.com \
--cc=syzbot+7c72edfb407b2bd866ce@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).