From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F18EC433DB for ; Fri, 25 Dec 2020 20:06:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BCAB7221FE for ; Fri, 25 Dec 2020 20:06:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726656AbgLYUGE (ORCPT ); Fri, 25 Dec 2020 15:06:04 -0500 Received: from mail-il1-f199.google.com ([209.85.166.199]:33737 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726345AbgLYUGE (ORCPT ); Fri, 25 Dec 2020 15:06:04 -0500 Received: by mail-il1-f199.google.com with SMTP id j20so4246179ilk.0 for ; Fri, 25 Dec 2020 12:05:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=jM+C3OOZ4ksBidecxlR1gd6x+PHtQDUO4e67dcNJLj4=; b=S1oEXqfb9m7AOpQlrGqh+1UJGisQULlK++4z2rfD5IkB8Zt0QSpTr4U0uUcud0rZ2p 4Zu8WQJV8vvr7ea3nLY3ed4hycgKy1T34/p97WI8vg1pcGz3qJUj0WFr0oGy2Kb0n3EY rbZnut64Sgb7zDsUuiNr7amKkQhRYJoA2js9VKnuO/jgRCwG9SZG12JOMUHAj8TZS6rg qkGyiLLAXD4X8oft3Zsbs+lFH5kOr7DMYsVzCgSx8bhwDBDCN5epjEpdmlE8DELv+L3A zgJe7nWPAG48n7Bu/6Zf3MZGq7AvHjn+Lzab6U3WCuuHTpR++xHYk/IOYLnXuwYqyXLH xZYw== X-Gm-Message-State: AOAM533XEdygnA/h+aqtJfb80ZZ5GO5J/eT6cN9n6SVHQtXaQDc+QkkZ BK88T/9Gi1rjtjcgqsTsxFayZxoo6CnBJrgdbkt+0ZLi1cLR X-Google-Smtp-Source: ABdhPJz5PicBs+l8RuC0Ux/HqsJa0Li8hBog6zkU9Hy3iPbwU1twzoW0XX/6SFGUGZ1Lf50F+u/y4VKIDU8zMydg96YIPQwitATo MIME-Version: 1.0 X-Received: by 2002:a05:6638:bc1:: with SMTP id g1mr30497549jad.27.1608926722967; Fri, 25 Dec 2020 12:05:22 -0800 (PST) Date: Fri, 25 Dec 2020 12:05:22 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000cad14c05b74f714c@google.com> Subject: UBSAN: shift-out-of-bounds in dummy_hub_control From: syzbot To: andreyknvl@gmail.com, andreyknvl@google.com, balbi@kernel.org, gregkh@linuxfoundation.org, gustavoars@kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: e37b12e4 Merge tag 'for-linus-5.11-ofs1' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17429937500000 kernel config: https://syzkaller.appspot.com/x/.config?x=98408202fed1f636 dashboard link: https://syzkaller.appspot.com/bug?extid=5925509f78293baa7331 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1781fc5b500000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157cd123500000 The issue was bisected to: commit 8442b02bf3c6770e0d7e7ea17be36c30e95987b6 Author: Andrey Konovalov Date: Mon Oct 21 14:20:58 2019 +0000 USB: dummy-hcd: increase max number of devices to 32 bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1631d0db500000 final oops: https://syzkaller.appspot.com/x/report.txt?x=1531d0db500000 console output: https://syzkaller.appspot.com/x/log.txt?x=1131d0db500000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+5925509f78293baa7331@syzkaller.appspotmail.com Fixes: 8442b02bf3c6 ("USB: dummy-hcd: increase max number of devices to 32") ================================================================================ UBSAN: shift-out-of-bounds in drivers/usb/gadget/udc/dummy_hcd.c:2293:33 shift exponent 257 is too large for 32-bit type 'int' CPU: 0 PID: 8526 Comm: syz-executor949 Not tainted 5.10.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:120 ubsan_epilogue+0xb/0x5a lib/ubsan.c:148 __ubsan_handle_shift_out_of_bounds.cold+0xb1/0x181 lib/ubsan.c:395 dummy_hub_control.cold+0x1a/0xbc drivers/usb/gadget/udc/dummy_hcd.c:2293 rh_call_control drivers/usb/core/hcd.c:683 [inline] rh_urb_enqueue drivers/usb/core/hcd.c:841 [inline] usb_hcd_submit_urb+0xcaa/0x22d0 drivers/usb/core/hcd.c:1544 usb_submit_urb+0x6e4/0x1560 drivers/usb/core/urb.c:585 usb_start_wait_urb+0x101/0x4c0 drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline] usb_control_msg+0x31c/0x4a0 drivers/usb/core/message.c:153 do_proc_control+0x4cb/0x9c0 drivers/usb/core/devio.c:1165 proc_control drivers/usb/core/devio.c:1191 [inline] usbdev_do_ioctl drivers/usb/core/devio.c:2535 [inline] usbdev_ioctl+0x12c1/0x3b20 drivers/usb/core/devio.c:2708 vfs_ioctl fs/ioctl.c:48 [inline] __do_sys_ioctl fs/ioctl.c:753 [inline] __se_sys_ioctl fs/ioctl.c:739 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x443f29 Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 fb d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007ffc10df4328 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00000000004002e0 RCX: 0000000000443f29 RDX: 0000000020000000 RSI: 00000000c0185500 RDI: 0000000000000003 RBP: 00000000006ce018 R08: 0000000000000000 R09: 00000000004002e0 R10: 000000000000000f R11: 0000000000000246 R12: 0000000000401bb0 R13: 0000000000401c40 R14: 0000000000000000 R15: 0000000000000000 ================================================================================ --- This report 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@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches