From: syzbot <syzbot+52ee52c330c2fcdade39@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: KASAN: stack-out-of-bounds Read in rb_erase (3)
Date: Sat, 07 Jul 2018 08:09:02 -0700 [thread overview]
Message-ID: <00000000000025545a05706a29d4@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 29119529d8de Merge tag 'for-linus-20180706' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e2550c400000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86
dashboard link: https://syzkaller.appspot.com/bug?extid=52ee52c330c2fcdade39
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1463ef48400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e481b2400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+52ee52c330c2fcdade39@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
==================================================================
BUG: KASAN: stack-out-of-bounds in ____rb_erase_color lib/rbtree.c:258
[inline]
BUG: KASAN: stack-out-of-bounds in rb_erase+0x19e9/0x3550 lib/rbtree.c:462
Read of size 8 at addr ffff8801c2dd7718 by task syz-executor396/4530
CPU: 1 PID: 4530 Comm: syz-executor396 Not tainted 4.18.0-rc3+ #134
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
print_address_description+0x6c/0x20b mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433
____rb_erase_color lib/rbtree.c:258 [inline]
rb_erase+0x19e9/0x3550 lib/rbtree.c:462
timerqueue_del+0x86/0x150 lib/timerqueue.c:87
__remove_hrtimer+0xa8/0x1b0 kernel/time/hrtimer.c:984
__run_hrtimer kernel/time/hrtimer.c:1380 [inline]
__hrtimer_run_queues+0x369/0x10c0 kernel/time/hrtimer.c:1460
hrtimer_interrupt+0x2f3/0x750 kernel/time/hrtimer.c:1518
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1025 [inline]
smp_apic_timer_interrupt+0x165/0x730 arch/x86/kernel/apic/apic.c:1050
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:863
</IRQ>
The buggy address belongs to the page:
page:ffffea00070b75c0 count:0 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x2fffc0000000000()
raw: 02fffc0000000000 0000000000000000 ffffffff070b0101 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8801c2dd7600: f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00
ffff8801c2dd7680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ffff8801c2dd7700: f1 f1 f1 f1 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2
^
ffff8801c2dd7780: f2 f2 f2 f2 00 f2 f2 f2 f2 f2 f2 f2 f8 f2 f2 f2
ffff8801c2dd7800: f2 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00 00 00 00
==================================================================
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2018-07-07 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 15:09 syzbot [this message]
2018-07-07 16:47 ` KASAN: stack-out-of-bounds Read in rb_erase (3) Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000025545a05706a29d4@google.com \
--to=syzbot+52ee52c330c2fcdade39@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.