linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+45862e7027be5d590577@syzkaller.appspotmail.com>
To: acme@kernel.org, alexander.shishkin@linux.intel.com,
	bp@alien8.de, hpa@zytor.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	x86@kernel.org
Subject: KASAN: out-of-bounds Read in pebs_update_state
Date: Thu, 14 May 2020 20:02:17 -0700	[thread overview]
Message-ID: <00000000000077346605a5a70a32@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    e99332e7 gcc-10: mark more functions __init to avoid secti..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e4a10c100000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8a96cf498e199d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=45862e7027be5d590577
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17bb1714100000

Bisection is inconclusive: the bug happens on the oldest tested release.

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12e02714100000
final crash:    https://syzkaller.appspot.com/x/report.txt?x=11e02714100000
console output: https://syzkaller.appspot.com/x/log.txt?x=16e02714100000

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

==================================================================
BUG: KASAN: out-of-bounds in pebs_update_adaptive_cfg arch/x86/events/intel/ds.c:991 [inline]
BUG: KASAN: out-of-bounds in pebs_update_state+0xc27/0xc80 arch/x86/events/intel/ds.c:1046
Read of size 8 at addr ffffc90004857428 by task syz-executor.1/8320

CPU: 0 PID: 8320 Comm: syz-executor.1 Not tainted 5.7.0-rc4-syzkaller #0
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+0x188/0x20d lib/dump_stack.c:118
 print_address_description.constprop.0.cold+0x5/0x315 mm/kasan/report.c:382
 __kasan_report.cold+0x35/0x4d mm/kasan/report.c:511
 kasan_report+0x33/0x50 mm/kasan/common.c:625
 pebs_update_adaptive_cfg arch/x86/events/intel/ds.c:991 [inline]
 pebs_update_state+0xc27/0xc80 arch/x86/events/intel/ds.c:1046
 </IRQ>


Memory state around the buggy address:
 ffffc90004857300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90004857380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004857400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                     ^
 ffffc90004857480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90004857500: 00 00 00 00 00 00 00 00 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#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

             reply	other threads:[~2020-05-15  3:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  3:02 syzbot [this message]
2020-08-15 20:03 ` KASAN: out-of-bounds Read in pebs_update_state syzbot

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=00000000000077346605a5a70a32@google.com \
    --to=syzbot+45862e7027be5d590577@syzkaller.appspotmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).