Dear kernel developers,
I found that KASAN: use-after-free Read in ath9k_hif_usb_rx_cb (2) and
"KASAN: slab-out-of-bounds Read in ath9k_hif_usb_rx_cb (2)" should
share the same root cause.
The reasons for my above statement, 1) the stack trace is the same;
2) we observed two crash
syzbot has found a reproducer for the following issue on:
HEAD commit:3650b228 Linux 5.10-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=14485e5050
kernel config: https://syzkaller.a
Hello,
syzbot found the following issue on:
HEAD commit:ab4dc051 usb: mtu3: simplify mtu3_req_complete()
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=11c0666c90
kernel config: https:/
syzbot has found a reproducer for the following crash on:
HEAD commit:806d8acc USB: dummy-hcd: use configurable endpoint naming ..
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=113b269a10
kernel config: https://syz
Hello,
syzbot found the following crash on:
HEAD commit:806d8acc USB: dummy-hcd: use configurable endpoint naming ..
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=1147bce610
kernel config: https://syzkaller.appspo