panic: UBSan: Undefined Behavior in /syzkall[ 58.ADDR] er/managers/netbsd-kubsan/kernel/sys/net/rtsock_shared.c:LINE, m

0 views
Skip to first unread message

syzbot

unread,
Nov 24, 2019, 9:29:09 AM11/24/19
to syzkaller-...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: fc618c23 PR port-arm/54702
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12028d5ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=824b23e1f4b6c76b
dashboard link: https://syzkaller.appspot.com/bug?extid=587b2285790c92cdea9a

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+587b22...@syzkaller.appspotmail.com

[ 58.1419844] panic: UBSan: Undefined Behavior in /syzkall[ 58.1419844]
er/managers/netbsd-kubsan/kernel/sys/net/rtsock_shared.c:631:41, member
access within misaligned address 0xfffff5f53fd0a60c for type 'struct
rt_msghdr50' which requires 8 byte alignment

[ 58.1419844] cpu0: Begin traceback...
[ 58.1419844] vpanic() at netbsd:vpanic+0x2aa sys/kern/subr_prf.c:336
[ 58.1419844] isAlreadyReported() at netbsd:isAlreadyReported
[ 58.1419844] HandleTypeMismatch.part.1() at
netbsd:HandleTypeMismatch.part.1+0xcc
[ 58.1419844] HandleTypeMismatch() at netbsd:HandleTypeMismatch+0x7b
sys/../common/lib/libc/misc/ubsan.c:408
[ 58.1419844] compat_50_route_output() at
netbsd:compat_50_route_output+0x1a4a sys/net/rtsock_shared.c:631
[ 58.1419844] raw_send() at netbsd:raw_send+0x20b sys/net/raw_usrreq.c:182
[ 58.1419844] compat_50_route_send_wrapper() at
netbsd:compat_50_route_send_wrapper+0x9f compat_50_route_send
sys/net/rtsock_shared.c:464 [inline]
[ 58.1419844] compat_50_route_send_wrapper() at
netbsd:compat_50_route_send_wrapper+0x9f sys/net/rtsock_shared.c:1663
[ 58.1419844] sosend() at netbsd:sosend+0x15ac sys/kern/uipc_socket.c:1059
[ 58.1419844] do_sys_sendmsg_so() at netbsd:do_sys_sendmsg_so+0x53d
sys/kern/uipc_syscalls.c:629
[ 58.1419844] do_sys_sendmsg() at netbsd:do_sys_sendmsg+0xcd
sys/kern/uipc_syscalls.c:679
[ 58.1419844] sys_sendto() at netbsd:sys_sendto+0xc9
sys/kern/uipc_syscalls.c:514
[ 58.1419844] sys___syscall() at netbsd:sys___syscall+0x1c8 sy_call
sys/sys/syscallvar.h:65 [inline]
[ 58.1419844] sys___syscall() at netbsd:sys___syscall+0x1c8
sys/kern/sys_syscall.c:77
[ 58.1419844] syscall() at netbsd:syscall+0x29a sy_call
sys/sys/syscallvar.h:65 [inline]
[ 58.1419844] syscall() at netbsd:syscall+0x29a sy_invoke
sys/sys/syscallvar.h:94 [inline]
[ 58.1419844] syscall() at netbsd:syscall+0x29a
sys/arch/x86/x86/syscall.c:138
[ 58.1419844] --- syscall (number 198) ---
[ 58.1419844] Skipping crash dump on recursive panic
[ 58.1419844] panic: UBSan: Undefined Behavior in
/syzkaller/managers/netbsd-kubsan/kernel/sys/arch/amd64/amd64/db_machdep.c:153:24,
member access within misaligned address 0x6 for type 'struct x86_64_frame'
which requires 8 byte alignment

[ 58.1419844] Faulted in mid-traceback; aborting...
[ 58.1419844] fatal breakpoint trap in supervisor mode
[ 58.1419844] trap type 1 code 0 rip 0xffffffff8021ddbd cs 0x8 rflags
0x282 cr2 0x20001000 ilevel 0x8 rsp 0xffff8e00b3b405f0
[ 58.1419844] curlwp 0xfffff5f551aeb280 pid 289.3 lowest kstack
0xffff8e00b3b3e2c0
Stopped in pid 289.3 (syz-executor.3) at netbsd:breakpoint+0x5:
leave
?
breakpoint() at netbsd:breakpoint+0x5
db_panic() at netbsd:db_panic+0x109 sys/ddb/db_panic.c:67
vpanic() at netbsd:vpanic+0x2aa sys/kern/subr_prf.c:336
isAlreadyReported() at netbsd:isAlreadyReported
HandleTypeMismatch.part.1() at netbsd:HandleTypeMismatch.part.1+0xcc
HandleTypeMismatch() at netbsd:HandleTypeMismatch+0x7b
sys/../common/lib/libc/misc/ubsan.c:408
db_nextframe() at netbsd:db_nextframe+0x6f6
sys/arch/amd64/amd64/db_machdep.c:153
db_stack_trace_print() at netbsd:db_stack_trace_print+0x2c4
sys/arch/x86/x86/db_trace.c:277
db_panic() at netbsd:db_panic+0xa3 x86_curcpu
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:67 [inline]
db_panic() at netbsd:db_panic+0xa3 sys/ddb/db_panic.c:57
vpanic() at netbsd:vpanic+0x2aa sys/kern/subr_prf.c:336
isAlreadyReported() at netbsd:isAlreadyReported
HandleTypeMismatch.part.1() at netbsd:HandleTypeMismatch.part.1+0xcc
HandleTypeMismatch() at netbsd:HandleTypeMismatch+0x7b
sys/../common/lib/libc/misc/ubsan.c:408
compat_50_route_output() at netbsd:compat_50_route_output+0x1a4a
sys/net/rtsock_shared.c:631
raw_send() at netbsd:raw_send+0x20b sys/net/raw_usrreq.c:182
compat_50_route_send_wrapper() at netbsd:compat_50_route_send_wrapper+0x9f
compat_50_route_send sys/net/rtsock_shared.c:464 [inline]
compat_50_route_send_wrapper() at netbsd:compat_50_route_send_wrapper+0x9f
sys/net/rtsock_shared.c:1663
sosend() at netbsd:sosend+0x15ac sys/kern/uipc_socket.c:1059
do_sys_sendmsg_so() at netbsd:do_sys_sendmsg_so+0x53d
sys/kern/uipc_syscalls.c:629
do_sys_sendmsg() at netbsd:do_sys_sendmsg+0xcd sys/kern/uipc_syscalls.c:679
sys_sendto() at netbsd:sys_sendto+0xc9 sys/kern/uipc_syscalls.c:514
sys___syscall() at netbsd:sys___syscall+0x1c8 sy_call
sys/sys/syscallvar.h:65 [inline]
sys___syscall() at netbsd:sys___syscall+0x1c8 sys/kern/sys_syscall.c:77
syscall() at netbsd:syscall+0x29a sy_call sys/sys/syscallvar.h:65 [inline]
syscall() at netbsd:syscall+0x29a sy_invoke sys/sys/syscallvar.h:94 [inline]
syscall() at netbsd:syscall+0x29a sys/arch/x86/x86/syscall.c:138
--- syscall (number 198) ---
[ 58.1419844] Skipping crash dump on recursive panic
[ 58.1419844] panic: UBSan: Undefined Behavior in
/syzkaller/managers/netbsd-kubsan/kernel/sys/arch/amd64/amd64/db_machdep.c:154:14,
member access within misaligned address 0x6 for type 'struct x86_64_frame'
which requires 8 byte alignment

[ 58.1419844] Faulted in mid-traceback; aborting...
[ 58.1419844] fatal breakpoint trap in supervisor mode
[ 58.1419844] trap type 1 code 0 rip 0xffffffff8021ddbd cs 0x8 rflags
0x282 cr2 0x20001000 ilevel 0x8 rsp 0xffff8e00b3b3f2f0
[ 58.1419844] curlwp 0xfffff5f551aeb280 pid 289.3 lowest kstack
0xffff8e00b3b3e2c0
Stopped in pid 289.3 (syz-executor.3) at netbsd:breakpoint+0x5:
leave


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Maxime Villard

unread,
Nov 26, 2019, 10:36:35 AM11/26/19
to syzbot, syzkaller-...@googlegroups.com
dup but garbage, close

#syz invalid
Reply all
Reply to author
Forward
0 new messages