Hello,
syzbot found the following crash on:
HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
git tree: kmsan
console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
compiler: clang version 9.0.0 (/home/glider/llvm/clang
80fee25776c2fb61e74c1ecb1a523375c2500b69)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: [email protected]
usb 1-1: config 0 has no interface number 0
usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,
bcdDevice=8b.53
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1: config 0 descriptor??
peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
==================================================================
BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50
drivers/usb/core/urb.c:405
CPU: 0 PID: 3359 Comm: kworker/0:2 Not tainted 5.2.0-rc4+ #7
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: usb_hub_wq hub_event
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x191/0x1f0 lib/dump_stack.c:113
kmsan_report+0x162/0x2d0 mm/kmsan/kmsan.c:611
kmsan_internal_check_memory+0x974/0xa80 mm/kmsan/kmsan.c:705
kmsan_handle_urb+0x28/0x40 mm/kmsan/kmsan_hooks.c:617
usb_submit_urb+0x7ef/0x1f50 drivers/usb/core/urb.c:405
usb_start_wait_urb+0x143/0x410 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x49f/0x7f0 drivers/usb/core/message.c:156
pcan_usb_pro_send_req+0x26b/0x3e0
drivers/net/can/usb/peak_usb/pcan_usb_pro.c:336
pcan_usb_fd_drv_loaded drivers/net/can/usb/peak_usb/pcan_usb_fd.c:460
[inline]
pcan_usb_fd_init+0x16ee/0x1900
drivers/net/can/usb/peak_usb/pcan_usb_fd.c:885
peak_usb_create_dev drivers/net/can/usb/peak_usb/pcan_usb_core.c:809
[inline]
peak_usb_probe+0x1416/0x1b20
drivers/net/can/usb/peak_usb/pcan_usb_core.c:907
usb_probe_interface+0xd19/0x1310 drivers/usb/core/driver.c:361
really_probe+0x1344/0x1d90 drivers/base/dd.c:513
driver_probe_device+0x1ba/0x510 drivers/base/dd.c:670
__device_attach_driver+0x5b8/0x790 drivers/base/dd.c:777
bus_for_each_drv+0x28e/0x3b0 drivers/base/bus.c:454
__device_attach+0x489/0x750 drivers/base/dd.c:843
device_initial_probe+0x4a/0x60 drivers/base/dd.c:890
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at [email protected].
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
On Tue, 30 Jul 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> git tree: kmsan
> console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> compiler: clang version 9.0.0 (/home/glider/llvm/clang
> 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: [email protected]
>
> usb 1-1: config 0 has no interface number 0
> usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,
> bcdDevice=8b.53
> usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> usb 1-1: config 0 descriptor??
> peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
> ==================================================================
> BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50
> drivers/usb/core/urb.c:405
What does "kernel-usb-infoleak" mean?
Alan Stern
On Tue, Jul 30, 2019 at 4:17 PM Alan Stern <[email protected]> wrote:
>
> On Tue, 30 Jul 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> > git tree: kmsan
> > console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> > dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> > compiler: clang version 9.0.0 (/home/glider/llvm/clang
> > 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: [email protected]
> >
> > usb 1-1: config 0 has no interface number 0
> > usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,
> > bcdDevice=8b.53
> > usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > usb 1-1: config 0 descriptor??
> > peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
> > ==================================================================
> > BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50
> > drivers/usb/core/urb.c:405
>
> What does "kernel-usb-infoleak" mean?
That means that the kernel put some uninitialized data into a request
that was sent to a USB device.
>
> Alan Stern
>
On Tue, Jul 30, 2019 at 4:20 PM Andrey Konovalov <[email protected]> wrote:
>
> On Tue, Jul 30, 2019 at 4:17 PM Alan Stern <[email protected]> wrote:
> >
> > On Tue, 30 Jul 2019, syzbot wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> > > git tree: kmsan
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> > > compiler: clang version 9.0.0 (/home/glider/llvm/clang
> > > 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: [email protected]
> > >
> > > usb 1-1: config 0 has no interface number 0
> > > usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,
> > > bcdDevice=8b.53
> > > usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > usb 1-1: config 0 descriptor??
> > > peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
> > > ==================================================================
> > > BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50
> > > drivers/usb/core/urb.c:405
> >
> > What does "kernel-usb-infoleak" mean?
>
> That means that the kernel put some uninitialized data into a request
> that was sent to a USB device.
Here's a better report for this bug:
https://syzkaller.appspot.com/text?tag=CrashReport&x=11dae8ec600000
This is a real bug, I was able to reproduce it with a hardware
reproducer and leak some kernel pointers AFAIR.
>
> >
> > Alan Stern
> >
On Tue, Jul 30, 2019 at 4:22 PM 'Andrey Konovalov' via syzkaller-bugs
<[email protected]> wrote:
>
> On Tue, Jul 30, 2019 at 4:20 PM Andrey Konovalov <[email protected]> wrote:
> >
> > On Tue, Jul 30, 2019 at 4:17 PM Alan Stern <[email protected]> wrote:
> > >
> > > On Tue, 30 Jul 2019, syzbot wrote:
> > >
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> > > > git tree: kmsan
> > > > console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> > > > kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> > > > dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> > > > compiler: clang version 9.0.0 (/home/glider/llvm/clang
> > > > 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> > > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> > > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
> > > >
> > > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > > Reported-by: [email protected]
> > > >
> > > > usb 1-1: config 0 has no interface number 0
> > > > usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,
> > > > bcdDevice=8b.53
> > > > usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > > usb 1-1: config 0 descriptor??
> > > > peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
> > > > ==================================================================
> > > > BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50
> > > > drivers/usb/core/urb.c:405
> > >
> > > What does "kernel-usb-infoleak" mean?
> >
> > That means that the kernel put some uninitialized data into a request
> > that was sent to a USB device.
>
> Here's a better report for this bug:
Yes, for some reason syzkaller lost half of the original report when
reproducing the bug.
> https://syzkaller.appspot.com/text?tag=CrashReport&x=11dae8ec600000
>
> This is a real bug, I was able to reproduce it with a hardware
> reproducer and leak some kernel pointers AFAIR.
> >
> > >
> > > Alan Stern
> > >
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/CAAeHK%2Bz50rsvQypF5AivYJh0wQ04XAueC%3DMs2cPt3%2BQuN1%2BKGg%40mail.gmail.com.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg