From: syzbot <syzbot+e1fe9f44fb8ecf4fb5dd@syzkaller.appspotmail.com>
To: alsa-devel-owner@alsa-project.org, alsa-devel@alsa-project.org,
gustavo@embeddedor.com, linux-kernel@vger.kernel.org,
perex@perex.cz, syzkaller-bugs@googlegroups.com, tiwai@suse.com,
tiwai@suse.de
Subject: Re: KASAN: slab-out-of-bounds Read in resample_shrink
Date: Sat, 07 Mar 2020 23:34:02 -0800 [thread overview]
Message-ID: <00000000000025d0e305a052e97f@google.com> (raw)
In-Reply-To: <000000000000b25ea005a02bcf21@google.com>
syzbot has bisected this bug to:
commit ca0214ee2802dd47239a4e39fb21c5b00ef61b22
Author: Takashi Iwai <tiwai@suse.de>
Date: Fri Mar 22 15:00:54 2019 +0000
ALSA: pcm: Fix possible OOB access in PCM oss plugins
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101931fde00000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=121931fde00000
console output: https://syzkaller.appspot.com/x/log.txt?x=141931fde00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
dashboard link: https://syzkaller.appspot.com/bug?extid=e1fe9f44fb8ecf4fb5dd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160e2e91e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125f09fde00000
Reported-by: syzbot+e1fe9f44fb8ecf4fb5dd@syzkaller.appspotmail.com
Fixes: ca0214ee2802 ("ALSA: pcm: Fix possible OOB access in PCM oss plugins")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-03-08 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 8:55 KASAN: slab-out-of-bounds Read in resample_shrink syzbot
2020-03-08 7:34 ` syzbot [this message]
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=00000000000025d0e305a052e97f@google.com \
--to=syzbot+e1fe9f44fb8ecf4fb5dd@syzkaller.appspotmail.com \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.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.