Hello,
syzbot found the following issue on:
HEAD commit: 05ef4ccb5774 Revert "ipvlan: properly track tx_errors"
git tree: android13-5.15-lts
console+strace:
https://syzkaller.appspot.com/x/log.txt?x=17db38f1e80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=efa97e9d20fc8142
dashboard link:
https://syzkaller.appspot.com/bug?extid=4e6d9667667204fca9b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=17675201e80000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=127fe021e80000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/08c970a04252/disk-05ef4ccb.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ba3530601846/vmlinux-05ef4ccb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/b019552eabf4/bzImage-05ef4ccb.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4e6d96...@syzkaller.appspotmail.com
================================================================================
UBSAN: shift-out-of-bounds in kernel/bpf/verifier.c:7979:63
shift exponent 1073741824 is too large for 32-bit type 's32' (aka 'int')
CPU: 0 PID: 292 Comm: syz-executor319 Not tainted 5.15.139-syzkaller-00529-g05ef4ccb5774 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x3bf/0x420 lib/ubsan.c:321
scalar32_min_max_arsh+0x622/0x6c0 kernel/bpf/verifier.c:7979
adjust_scalar_min_max_vals kernel/bpf/verifier.c:8167 [inline]
adjust_reg_min_max_vals+0x3d1d/0x6360 kernel/bpf/verifier.c:8268
check_alu_op kernel/bpf/verifier.c:8439 [inline]
do_check+0x94d9/0xf2c0 kernel/bpf/verifier.c:11183
do_check_common+0x909/0x1290 kernel/bpf/verifier.c:13398
do_check_main kernel/bpf/verifier.c:13461 [inline]
bpf_check+0x3835/0x12bf0 kernel/bpf/verifier.c:14032
bpf_prog_load+0x12ac/0x1b50 kernel/bpf/syscall.c:2327
__sys_bpf+0x4bc/0x760 kernel/bpf/syscall.c:4618
__do_sys_bpf kernel/bpf/syscall.c:4722 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4720 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4720
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff1d19493e9
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe67a82798 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007ffe67a82978 RCX: 00007ff1d19493e9
RDX: 0000000000000048 RSI: 00000000200054c0 RDI: 0000000000000005
RBP: 00007ff1d19bc610 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe67a82968 R14: 0000000000000001 R15: 0000000000000001
</TASK>
================================================================================
================================================================================
UBSAN: shift-out-of-bounds in kernel/bpf/verifier.c:7980:63
shift exponent 1073741824 is too large for 32-bit type 's32' (aka 'int')
CPU: 0 PID: 292 Comm: syz-executor319 Not tainted 5.15.139-syzkaller-00529-g05ef4ccb5774 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x3bf/0x420 lib/ubsan.c:321
scalar32_min_max_arsh+0x676/0x6c0 kernel/bpf/verifier.c:7980
adjust_scalar_min_max_vals kernel/bpf/verifier.c:8167 [inline]
adjust_reg_min_max_vals+0x3d1d/0x6360 kernel/bpf/verifier.c:8268
check_alu_op kernel/bpf/verifier.c:8439 [inline]
do_check+0x94d9/0xf2c0 kernel/bpf/verifier.c:11183
do_check_common+0x909/0x1290 kernel/bpf/verifier.c:13398
do_check_main kernel/bpf/verifier.c:13461 [inline]
bpf_check+0x3835/0x12bf0 kernel/bpf/verifier.c:14032
bpf_prog_load+0x12ac/0x1b50 kernel/bpf/syscall.c:2327
__sys_bpf+0x4bc/0x760 kernel/bpf/syscall.c:4618
__do_sys_bpf kernel/bpf/syscall.c:4722 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4720 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4720
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff1d19493e9
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe67a82798 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007ffe67a82978 RCX: 00007ff1d19493e9
RDX: 0000000000000048 RSI: 00000000200054c0 RDI: 0000000000000005
RBP: 00007ff1d19bc610 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe67a82968 R14: 0000000000000001 R15: 0000000000000001
</TASK>
=================
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup