In the Linux kernel, the following vulnerability has been resolved:
net: USB: Fix wrong-direction WARNING in plusb.c
The syzbot fuzzer detected a bug in the plusb network driver: A zero-length control-OUT transfer was treated as a read instead of a write. In modern kernels this error provokes a WARNING:
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0 WARNING: CPU: 0 PID: 4645 at drivers/usb/core/urb.c:411 usbsubmiturb+0x14a7/0x1880 drivers/usb/core/urb.c:411 Modules linked in: CPU: 1 PID: 4645 Comm: dhcpcd Not tainted 6.2.0-rc6-syzkaller-00050-g9f266ccaa2f5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 RIP: 0010:usbsubmiturb+0x14a7/0x1880 drivers/usb/core/urb.c:411 ... Call Trace: <TASK> usbstartwaiturb+0x101/0x4b0 drivers/usb/core/message.c:58 usbinternalcontrolmsg drivers/usb/core/message.c:102 [inline] usbcontrolmsg+0x320/0x4a0 drivers/usb/core/message.c:153 _usbnetreadcmd+0xb9/0x390 drivers/net/usb/usbnet.c:2010 usbnetreadcmd+0x96/0xf0 drivers/net/usb/usbnet.c:2068 plvendorreq drivers/net/usb/plusb.c:60 [inline] plsetQuickLinkfeatures drivers/net/usb/plusb.c:75 [inline] plreset+0x2f/0xf0 drivers/net/usb/plusb.c:85 usbnetopen+0xcc/0x5d0 drivers/net/usb/usbnet.c:889 _devopen+0x297/0x4d0 net/core/dev.c:1417 _devchangeflags+0x587/0x750 net/core/dev.c:8530 devchangeflags+0x97/0x170 net/core/dev.c:8602 devinetioctl+0x15a2/0x1d70 net/ipv4/devinet.c:1147 inetioctl+0x33f/0x380 net/ipv4/afinet.c:979 sockdoioctl+0xcc/0x230 net/socket.c:1169 sockioctl+0x1f8/0x680 net/socket.c:1286 vfsioctl fs/ioctl.c:51 [inline] _dosysioctl fs/ioctl.c:870 [inline] _sesysioctl fs/ioctl.c:856 [inline] _x64sysioctl+0x197/0x210 fs/ioctl.c:856 dosyscallx64 arch/x86/entry/common.c:50 [inline] dosyscall64+0x39/0xb0 arch/x86/entry/common.c:80 entrySYSCALL64after_hwframe+0x63/0xcd
The fix is to call usbnetwritecmd() instead of usbnetreadcmd() and remove the USBDIRIN flag.