| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <0000000000009767ec0619fe6a1d@google.com> Date: Mon, 03 Jun 2024 08:59:20 -0700 From: syzbot <syzbot+628f93722c08dc5aabe0@...kaller.appspotmail.com> To: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, syzkaller-bugs@...glegroups.com Subject: [syzbot] [net?] UBSAN: array-index-out-of-bounds in llc_conn_state_process (2) Hello, syzbot found the following issue on: HEAD commit: 6d7ddd805123 Merge tag 'soc-fixes-6.9-3' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12596604980000 kernel config: https://syzkaller.appspot.com/x/.config?x=7144b4fe7fbf5900 dashboard link: https://syzkaller.appspot.com/bug?extid=628f93722c08dc5aabe0 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4d60cb47fbb1/disk-6d7ddd80.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/f3ff90de7db5/vmlinux-6d7ddd80.xz kernel image: https://storage.googleapis.com/syzbot-assets/d452970444cd/bzImage-6d7ddd80.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+628f93722c08dc5aabe0@...kaller.appspotmail.com ------------[ cut here ]------------ UBSAN: array-index-out-of-bounds in net/llc/llc_conn.c:694:24 index -1 is out of range for type 'int [12][5]' CPU: 0 PID: 15346 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-00023-g6d7ddd805123 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:114 ubsan_epilogue lib/ubsan.c:231 [inline] __ubsan_handle_out_of_bounds+0x110/0x150 lib/ubsan.c:429 llc_find_offset net/llc/llc_conn.c:694 [inline] llc_qualify_conn_ev net/llc/llc_conn.c:401 [inline] llc_conn_service net/llc/llc_conn.c:366 [inline] llc_conn_state_process+0x1381/0x14e0 net/llc/llc_conn.c:72 llc_process_tmr_ev net/llc/llc_c_ac.c:1445 [inline] llc_conn_tmr_common_cb+0x450/0x8e0 net/llc/llc_c_ac.c:1331 call_timer_fn+0x1a0/0x610 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers+0x74b/0xaf0 kernel/time/timer.c:2418 __run_timer_base kernel/time/timer.c:2429 [inline] __run_timer_base kernel/time/timer.c:2422 [inline] run_timer_base+0x111/0x190 kernel/time/timer.c:2438 run_timer_softirq+0x1a/0x40 kernel/time/timer.c:2448 handle_softirqs+0x216/0x8f0 kernel/softirq.c:554 __do_softirq kernel/softirq.c:588 [inline] invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu kernel/softirq.c:637 [inline] irq_exit_rcu+0xbb/0x120 kernel/softirq.c:649 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0x95/0xb0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x1f2/0x560 kernel/locking/lockdep.c:5722 Code: c1 05 0a 93 96 7e 83 f8 01 0f 85 ea 02 00 00 9c 58 f6 c4 02 0f 85 d5 02 00 00 48 85 ed 74 01 fb 48 b8 00 00 00 00 00 fc ff df <48> 01 c3 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 48 8b 84 24 RSP: 0018:ffffc900033df5e0 EFLAGS: 00000206 RAX: dffffc0000000000 RBX: 1ffff9200067bebe RCX: ffffffff816b01de RDX: 0000000000000001 RSI: ffffffff8b0cb100 RDI: ffffffff8b6f57a0 RBP: 0000000000000200 R08: 0000000000000000 R09: fffffbfff27bba45 R10: ffffffff93ddd22f R11: 0000000000000000 R12: 0000000000000001 R13: 0000000000000000 R14: ffff888073a52d80 R15: 0000000000000000 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 __unix_dgram_recvmsg+0x267/0x1000 net/unix/af_unix.c:2426 unix_dgram_recvmsg+0xd0/0x110 net/unix/af_unix.c:2531 sock_recvmsg_nosec net/socket.c:1046 [inline] ____sys_recvmsg+0x5fe/0x6b0 net/socket.c:2801 ___sys_recvmsg+0x115/0x1a0 net/socket.c:2845 do_recvmmsg+0x2ba/0x750 net/socket.c:2939 __sys_recvmmsg net/socket.c:3018 [inline] __do_sys_recvmmsg net/socket.c:3041 [inline] __se_sys_recvmmsg net/socket.c:3034 [inline] __x64_sys_recvmmsg+0x239/0x290 net/socket.c:3034 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6eefa7dd69 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6ef08350c8 EFLAGS: 00000246 ORIG_RAX: 000000000000012b RAX: ffffffffffffffda RBX: 00007f6eefbac050 RCX: 00007f6eefa7dd69 RDX: 0000000000010106 RSI: 00000000200000c0 RDI: 0000000000000005 RBP: 00007f6eefaca49e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007f6eefbac050 R15: 00007ffeec7fdc18 </TASK> ---[ end trace ]--- ---------------- Code disassembly (best guess): 0: c1 05 0a 93 96 7e 83 roll $0x83,0x7e96930a(%rip) # 0x7e969311 7: f8 clc 8: 01 0f add %ecx,(%rdi) a: 85 ea test %ebp,%edx c: 02 00 add (%rax),%al e: 00 9c 58 f6 c4 02 0f add %bl,0xf02c4f6(%rax,%rbx,2) 15: 85 d5 test %edx,%ebp 17: 02 00 add (%rax),%al 19: 00 48 85 add %cl,-0x7b(%rax) 1c: ed in (%dx),%eax 1d: 74 01 je 0x20 1f: fb sti 20: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax 27: fc ff df * 2a: 48 01 c3 add %rax,%rbx <-- trapping instruction 2d: 48 c7 03 00 00 00 00 movq $0x0,(%rbx) 34: 48 c7 43 08 00 00 00 movq $0x0,0x8(%rbx) 3b: 00 3c: 48 rex.W 3d: 8b .byte 0x8b 3e: 84 .byte 0x84 3f: 24 .byte 0x24 --- 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@...glegroups.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 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
Powered by blists - more mailing lists