KASAN: stack-out-of-bounds Read in __tlb_remove_page_size

8 views
Skip to first unread message

syzbot

unread,
Jul 21, 2018, 2:29:04 PM7/21/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 8ae71e76cf1f Merge branch 'bpf-offload-sharing'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=171931c2400000
kernel config: https://syzkaller.appspot.com/x/.config?x=89129667b46496c3
dashboard link: https://syzkaller.appspot.com/bug?extid=35414afaff60f0fa7b91
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ak...@linux-foundation.org dan.j.w...@intel.com
jgl...@redhat.com kirill....@linux.intel.com
ldu...@linux.vnet.ibm.com linux-...@vger.kernel.org linu...@kvack.org
mho...@suse.com min...@kernel.org ross.z...@linux.intel.com
wi...@infradead.org ying....@intel.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+35414a...@syzkaller.appspotmail.com

==================================================================
PANIC: double fault, error_code: 0x0
BUG: KASAN: stack-out-of-bounds in __tlb_remove_page_size+0x426/0x500
mm/memory.c:314
Read of size 4 at addr ffff880198ac5008 by task modprobe/23657
CPU: 0 PID: 23642 Comm: syz-executor6 Not tainted 4.18.0-rc3+ #58

CPU: 1 PID: 23657 Comm: modprobe Not tainted 4.18.0-rc3+ #58
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
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
Call Trace:
Code: 41
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
57 41
89 cf
41 56
41
55 49
print_address_description+0x6c/0x20b mm/kasan/report.c:256
89 fd
41
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412
54 45
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:432
__tlb_remove_page_size+0x426/0x500 mm/memory.c:314
89
__tlb_remove_page include/asm-generic/tlb.h:150 [inline]
zap_pte_range mm/memory.c:1336 [inline]
zap_pmd_range mm/memory.c:1437 [inline]
zap_pud_range mm/memory.c:1466 [inline]
zap_p4d_range mm/memory.c:1487 [inline]
unmap_page_range+0x1059/0x2220 mm/memory.c:1508
cc
53
65 4c
8b
34
25 40
ee 01
00 48
83 e4
f0 48
81
ec
60 03
00 00
48
8b 45
unmap_single_vma+0x1a0/0x310 mm/memory.c:1553
10 <89>
unmap_vmas+0x120/0x1f0 mm/memory.c:1583
94 24
exit_mmap+0x2c2/0x5b0 mm/mmap.c:3105
80 00
00 00
__mmput kernel/fork.c:970 [inline]
mmput+0x265/0x620 kernel/fork.c:991
48 ba
00 00
00 00
00 fc
ff df
48 89
84 24
98
exit_mm kernel/exit.c:544 [inline]
do_exit+0xea9/0x2750 kernel/exit.c:852
RSP: 0018:ffff8801981ffe90 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 1ffff1003304004f RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff88f92620
RBP: ffff880198200220 R08: 0000000000000000 R09: 0000000000000000
R10: ffff880198b5fbe0 R11: ffff8801b1b9ccfb R12: 0000000000000000
R13: ffffffff88f92620 R14: ffff8801b1b9c580 R15: 0000000000000002
FS: 0000000000cd8940(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8801981ffe88 CR3: 000000019a5bf000 CR4: 00000000001406f0
DR0: 0000000020000000 DR1: 00000000200001c0 DR2: 0000000000000100
DR3: 0000000000000100 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 23, 2018, 2:00:19 AM7/23/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation, Daniel Borkmann
Looks like the same bpf map bug:

#syz fix: bpf: sockhash, disallow bpf_tcp_close and update in parallel
> --
> 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/00000000000041b65005718696cd%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages