UBSAN: shift-out-of-bounds in vcc_connect

Status: upstream: reported syz repro on 2026/08/23 18:53
Subsystems: net usb
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+6665d3db5fef15914802@syzkaller.appspotmail.com
First crash: 6d18h, last: 3d01h
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
0979e4ae assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ UBSAN: shift-out-of-bounds in vcc_connect 2026/08/20 00:00 2026/08/20 00:00 2026/08/20 00:58 1e72964b
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] net: atm: fix shift-out-of-bounds in __vcc_connect() 4 (4) 2026/08/26 12:32
[syzbot] [net?] [usb?] UBSAN: shift-out-of-bounds in vcc_connect 0 (2) 2026/08/24 01:58
Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/08/24 01:58 23m kartikey406@gmail.com patch upstream OK job log log

Sample crash report:
------------[ cut here ]------------
UBSAN: shift-out-of-bounds in net/atm/common.c:381:10
shift exponent -1 is negative
CPU: 0 UID: 0 PID: 6073 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 ubsan_epilogue+0xa/0x30 lib/ubsan.c:233
 __ubsan_handle_shift_out_of_bounds+0x279/0x2a0 lib/ubsan.c:494
 __vcc_connect net/atm/common.c:381 [inline]
 vcc_connect.cold+0xe0/0x123 net/atm/common.c:498
 pvc_bind+0x33f/0x460 net/atm/pvc.c:52
 __sys_bind_socket net/socket.c:1945 [inline]
 __sys_bind_socket net/socket.c:1937 [inline]
 __sys_bind+0x1a9/0x260 net/socket.c:1976
 __do_sys_bind net/socket.c:1981 [inline]
 __se_sys_bind net/socket.c:1979 [inline]
 __x64_sys_bind+0x72/0xb0 net/socket.c:1979
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6a3099e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff44bcea08 EFLAGS: 00000246 ORIG_RAX: 0000000000000031
RAX: ffffffffffffffda RBX: 00007f6a30c25fa0 RCX: 00007f6a3099e0d9
RDX: 000000000000000c RSI: 0000200000000100 RDI: 0000000000000004
RBP: 00007f6a30a35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6a30c25fac R14: 00007f6a30c25fa0 R15: 00007f6a30c25fa0
 </TASK>
---[ end trace ]---

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/19 23:36 upstream bd5f485f3f02 1e72964b .config strace log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root UBSAN: shift-out-of-bounds in vcc_connect
2026/08/19 21:06 upstream bd5f485f3f02 1e72964b .config strace log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root UBSAN: shift-out-of-bounds in vcc_connect
2026/08/23 11:43 upstream 2709dd5ae32f 1e72964b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 UBSAN: shift-out-of-bounds in vcc_connect
2026/08/19 18:44 upstream bd5f485f3f02 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root UBSAN: shift-out-of-bounds in vcc_connect
* Struck through repros no longer work on HEAD.