[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <001a113ff33e3aa97d055c4c7cd8@google.com>
Date: Tue, 24 Oct 2017 08:20:54 -0700
From: syzbot
<bot+a9d6dccad76c3e1f6cad1031d8f2292c4f4f0e1a@...kaller.appspotmail.com>
To: davem@...emloft.net, jon.maloy@...csson.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com,
tipc-discussion@...ts.sourceforge.net, ying.xue@...driver.com
Subject: KASAN: slab-out-of-bounds Read in tipc_nametbl_lookup_dst_nodes
Hello,
syzkaller hit the following crash on
80cee03bf1d626db0278271b505d7f5febb37bba
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers
BUG: KASAN: slab-out-of-bounds in tipc_nametbl_lookup_dst_nodes+0x4a3/0x4b0
net/tipc/name_table.c:670
Read of size 4 at addr ffff8801d3275f10 by task syzkaller601354/2981
CPU: 1 PID: 2981 Comm: syzkaller601354 Not tainted 4.13.0+ #42
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
print_address_description+0x73/0x250 mm/kasan/report.c:252
kasan_report_error mm/kasan/report.c:351 [inline]
kasan_report+0x24e/0x340 mm/kasan/report.c:409
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:429
tipc_nametbl_lookup_dst_nodes+0x4a3/0x4b0 net/tipc/name_table.c:670
tipc_sendmcast+0x704/0xe30 net/tipc/socket.c:767
__tipc_sendmsg+0xf49/0x1590 net/tipc/socket.c:971
__tipc_sendstream+0x8eb/0xc00 net/tipc/socket.c:1065
tipc_sendstream+0x50/0x70 net/tipc/socket.c:1039
tipc_send_packet+0x33/0x50 net/tipc/socket.c:1113
sock_sendmsg_nosec net/socket.c:633 [inline]
sock_sendmsg+0xca/0x110 net/socket.c:643
___sys_sendmsg+0x75b/0x8a0 net/socket.c:2049
__sys_sendmsg+0xe5/0x210 net/socket.c:2083
SYSC_sendmsg net/socket.c:2094 [inline]
SyS_sendmsg+0x2d/0x50 net/socket.c:2090
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x43fd79
RSP: 002b:00007ffcb61e8988 EFLAGS: 00000203 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043fd79
RDX: 0000000000000004 RSI: 00000000207ca000 RDI: 0000000000000003
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000203 R12: 00000000004016e0
R13: 0000000000401770 R14: 0000000000000000 R15: 0000000000000000
Allocated by task 1:
save_stack_trace+0x16/0x20 arch/x86/kernel/stacktrace.c:59
save_stack+0x43/0xd0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551
kmem_cache_alloc_trace+0x136/0x750 mm/slab.c:3627
kmalloc include/linux/slab.h:493 [inline]
kmalloc_array include/linux/slab.h:611 [inline]
kcalloc include/linux/slab.h:623 [inline]
tipc_subseq_alloc net/tipc/name_table.c:141 [inline]
tipc_nameseq_create+0xe8/0x540 net/tipc/name_table.c:152
tipc_nametbl_insert_publ+0xf77/0x17c0 net/tipc/name_table.c:476
tipc_nametbl_publish+0x2aa/0x4f0 net/tipc/name_table.c:701
tipc_sk_publish net/tipc/socket.c:2201 [inline]
tipc_bind+0x33a/0x700 net/tipc/socket.c:629
kernel_bind+0x62/0x80 net/socket.c:3285
tipc_create_listen_sock net/tipc/server.c:337 [inline]
tipc_open_listening_sock net/tipc/server.c:395 [inline]
tipc_server_start+0x3a1/0xb60 net/tipc/server.c:610
tipc_topsrv_start+0x64f/0x890 net/tipc/subscr.c:382
tipc_init_net+0x3cc/0x570 net/tipc/core.c:74
ops_init+0x10a/0x570 net/core/net_namespace.c:118
__register_pernet_operations net/core/net_namespace.c:879 [inline]
register_pernet_operations+0x45e/0x980 net/core/net_namespace.c:953
register_pernet_subsys+0x2a/0x40 net/core/net_namespace.c:995
tipc_init+0x83/0x104 net/tipc/core.c:136
do_one_initcall+0x9e/0x330 init/main.c:826
do_initcall_level init/main.c:892 [inline]
do_initcalls init/main.c:900 [inline]
do_basic_setup init/main.c:918 [inline]
kernel_init_freeable+0x469/0x521 init/main.c:1066
kernel_init+0x13/0x172 init/main.c:993
ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431
Freed by task 0:
(stack is not available)
The buggy address belongs to the object at ffff8801d3275f00
which belongs to the cache kmalloc-32 of size 32
The buggy address is located 16 bytes inside of
32-byte region [ffff8801d3275f00, ffff8801d3275f20)
The buggy address belongs to the page:
page:ffffea00074c9d40 count:1 mapcount:0 mapping:ffff8801d3275000
index:0xffff8801d3275fc1
flags: 0x200000000000100(slab)
raw: 0200000000000100 ffff8801d3275000 ffff8801d3275fc1 000000010000003f
raw: ffffea00074c8920 ffffea00074cea20 ffff8801dac001c0 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8801d3275e00: fb fb fb fb fc fc fc fc 00 00 00 fc fc fc fc fc
ffff8801d3275e80: 04 fc fc fc fc fc fc fc 00 00 00 fc fc fc fc fc
> ffff8801d3275f00: 00 00 fc fc fc fc fc fc 00 00 00 00 fc fc fc fc
^
ffff8801d3275f80: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc
ffff8801d3276000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.
syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
View attachment "config.txt" of type "text/plain" (123749 bytes)
Download attachment "raw.log" of type "application/octet-stream" (11312 bytes)
View attachment "repro.txt" of type "text/plain" (797 bytes)
Download attachment "repro.c" of type "application/octet-stream" (1923 bytes)
Powered by blists - more mailing lists