In the Linux kernel, the following vulnerability has been resolved:
wifi: ath9k: verify the expected usb_endpoints are present
The bug arises when a USB device claims to be an ATH9K but doesn't have the expected endpoints. (In this case there was an interrupt endpoint where the driver expected a bulk endpoint.) The kernel needs to be able to handle such devices without getting an internal error.
usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 3 PID: 500 at drivers/usb/core/urb.c:493 usbsubmiturb+0xce2/0x1430 drivers/usb/core/urb.c:493 Modules linked in: CPU: 3 PID: 500 Comm: kworker/3:2 Not tainted 5.10.135-syzkaller #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: events requestfirmwareworkfunc RIP: 0010:usbsubmiturb+0xce2/0x1430 drivers/usb/core/urb.c:493 Call Trace: ath9khifusballocrxurbs drivers/net/wireless/ath/ath9k/hifusb.c:908 [inline] ath9khifusballocurbs+0x75e/0x1010 drivers/net/wireless/ath/ath9k/hifusb.c:1019 ath9khifusbdevinit drivers/net/wireless/ath/ath9k/hifusb.c:1109 [inline] ath9khifusbfirmwarecb+0x142/0x530 drivers/net/wireless/ath/ath9k/hifusb.c:1242 requestfirmwareworkfunc+0x12e/0x240 drivers/base/firmwareloader/main.c:1097 processonework+0x9af/0x1600 kernel/workqueue.c:2279 workerthread+0x61d/0x12f0 kernel/workqueue.c:2425 kthread+0x3b4/0x4a0 kernel/kthread.c:313 retfromfork+0x22/0x30 arch/x86/entry/entry64.S:299
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.