lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 09 May 2019 04:37:06 -0700
From:   syzbot <syzbot+c1b25598aa60dcd47e78@...kaller.appspotmail.com>
To:     andreyknvl@...gle.com, linux-kernel@...r.kernel.org,
        linux-usb@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: WARNING: ath10k USB support is incomplete, don't expect anything to work!

Hello,

syzbot found the following crash on:

HEAD commit:    43151d6c 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=178c8394a00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4183eeef650d1234
dashboard link: https://syzkaller.appspot.com/bug?extid=c1b25598aa60dcd47e78
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17c22222a00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11ddce02a00000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+c1b25598aa60dcd47e78@...kaller.appspotmail.com

usb 1-1: new low-speed USB device number 2 using dummy_hcd
usb 1-1: config 0 has an invalid interface number: 93 but max is 0
usb 1-1: config 0 has no interface number 0
usb 1-1: New USB device found, idVendor=13b1, idProduct=0042,  
bcdDevice=f9.d4
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1: config 0 descriptor??
usb 1-1: WARNING: ath10k USB support is incomplete, don't expect anything  
to work!


---
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 syzkaller@...glegroups.com.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ