From: Johan Hovold <johan@kernel.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: syzbot <syzbot+ba00d6a2a24df57a94ca@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: slab-out-of-bounds Read in ld_usb_read
Date: Fri, 18 Oct 2019 16:41:22 +0200 [thread overview]
Message-ID: <20191018144122.GH21827@localhost> (raw)
In-Reply-To: <CAAeHK+xr9DoBHvF9B8+hN=4iEa-oVDogDtCcb04cxp+Mj3g-dg@mail.gmail.com>
On Mon, Aug 12, 2019 at 02:22:52PM +0200, Andrey Konovalov wrote:
> On Mon, Aug 12, 2019 at 2:18 PM syzbot
> <syzbot+ba00d6a2a24df57a94ca@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found 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=162aac02600000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=cfa2c18fb6a8068e
> > dashboard link: https://syzkaller.appspot.com/bug?extid=ba00d6a2a24df57a94ca
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1123edc2600000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16079d2c600000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+ba00d6a2a24df57a94ca@syzkaller.appspotmail.com
> >
> > ldusb 1-1:0.28: Read buffer overflow, -131386046930688 bytes dropped
> > ==================================================================
> > BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x124/0x150
> > lib/usercopy.c:27
> > Read of size 2147479552 at addr ffff8881cd580008 by task
> > syz-executor268/1890
> >
> > CPU: 0 PID: 1890 Comm: syz-executor268 Not tainted 5.3.0-rc2+ #25
> > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> > Google 01/01/2011
> > Call Trace:
> > __dump_stack lib/dump_stack.c:77 [inline]
> > dump_stack+0xca/0x13e lib/dump_stack.c:113
> > print_address_description+0x6a/0x32c mm/kasan/report.c:351
> > __kasan_report.cold+0x1a/0x33 mm/kasan/report.c:482
> > kasan_report+0xe/0x12 mm/kasan/common.c:612
> > check_memory_region_inline mm/kasan/generic.c:185 [inline]
> > check_memory_region+0x128/0x190 mm/kasan/generic.c:192
> > _copy_to_user+0x124/0x150 lib/usercopy.c:27
> > copy_to_user include/linux/uaccess.h:152 [inline]
> > ld_usb_read+0x31a/0x780 drivers/usb/misc/ldusb.c:495
>
> #syz dup: KASAN: use-after-free Read in ld_usb_release
#syz dup: KASAN: slab-out-of-bounds Read in ld_usb_read (3)
prev parent reply other threads:[~2019-10-18 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 12:18 KASAN: slab-out-of-bounds Read in ld_usb_read syzbot
2019-08-12 12:22 ` Andrey Konovalov
2019-10-18 14:41 ` 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=20191018144122.GH21827@localhost \
--to=johan@kernel.org \
--cc=andreyknvl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+ba00d6a2a24df57a94ca@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).