KASAN: stack-out-of-bounds Read in debug_check_no_obj_freed (2)

6 views
Skip to first unread message

syzbot

unread,
Jul 6, 2018, 9:19:03 PM7/6/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c48424d993fa samples/bpf: add .gitignore file
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=11e2a6d0400000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86
dashboard link: https://syzkaller.appspot.com/bug?extid=ddb0c85d8ae7e0c523a2
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [aarc...@redhat.com ak...@linux-foundation.org
dan.j.w...@intel.com dw...@amazon.co.uk linux-...@vger.kernel.org
linu...@kvack.org mho...@suse.com ol...@redhat.com rien...@google.com]

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+ddb0c8...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: stack-out-of-bounds in __debug_check_no_obj_freed
lib/debugobjects.c:775 [inline]
BUG: KASAN: stack-out-of-bounds in debug_check_no_obj_freed+0x467/0x595
lib/debugobjects.c:815
Read of size 8 at addr ffff8801d22d2d90 by task udevd/31943

CPU: 0 PID: 31943 Comm: udevd Not tainted 4.18.0-rc3+ #1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
PANIC: double fault, error_code: 0x0
Call Trace:
CPU: 1 PID: 31931 Comm: syz-executor1 Not tainted 4.18.0-rc3+ #1
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__lock_acquire+0x2e/0x5020 kernel/locking/lockdep.c:3294
Code: 41
57 41
89 cf
41 56
print_address_description+0x6c/0x20b mm/kasan/report.c:256
41
55 49
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412
89 fd
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433
41 54
__debug_check_no_obj_freed lib/debugobjects.c:775 [inline]
debug_check_no_obj_freed+0x467/0x595 lib/debugobjects.c:815
45 89
cc
53 65
kmem_cache_free+0x216/0x2d0 mm/slab.c:3755
4c 8b
remove_vma+0x164/0x1b0 mm/mmap.c:185
34 25
exit_mmap+0x365/0x5b0 mm/mmap.c:3116
40 ee
01 00
__mmput kernel/fork.c:970 [inline]
mmput+0x265/0x620 kernel/fork.c:991
48 83
e4 f0
48 81
ec 60
03 00
00 48
8b 45
exec_mmap fs/exec.c:1044 [inline]
flush_old_exec+0xbaf/0x2100 fs/exec.c:1276
10 <89>
94 24
80 00
00 00
48 ba
00
00 00
00
00 fc
ff df
48 89
84 24
98
load_elf_binary+0xa33/0x5610 fs/binfmt_elf.c:869
RSP: 0018:ffff8801cf5dfe70 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 1ffff10039ebc04a RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff88f92620
RBP: ffff8801cf5e01f8 R08: 0000000000000000 R09: 0000000000000000
R10: ffffed003b5e46d6 R11: ffff8801daf236b3 R12: 0000000000000000
R13: ffffffff88f92620 R14: ffff8801cf1de780 R15: 0000000000000002
FS: 00007f38716e9700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
search_binary_handler+0x17d/0x570 fs/exec.c:1653
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
exec_binprm fs/exec.c:1695 [inline]
__do_execve_file.isra.35+0x171d/0x2730 fs/exec.c:1819
CR2: ffff8801cf5dfe68 CR3: 00000001a1adc000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:


---
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#bug-status-tracking for how to communicate with
syzbot.

Dmitry Vyukov

unread,
Jul 7, 2018, 2:58:01 AM7/7/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
the bpf socket map bug

#syz invalid
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/000000000000dbb33705705e9084%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages