From: Takashi Iwai <tiwai@suse.de>
To: syzbot <syzbot+f153bde47a62e0b05f83@syzkaller.appspotmail.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
perex@perex.cz, syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: Re: KASAN: slab-out-of-bounds Read in linear_transfer (3)
Date: Wed, 04 Dec 2019 15:50:58 +0100 [thread overview]
Message-ID: <s5hlfrskuul.wl-tiwai@suse.de> (raw)
In-Reply-To: <000000000000055ac40598dc8d46@google.com>
On Wed, 04 Dec 2019 09:25:09 +0100,
syzbot wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 76bb8b05 Merge tag 'kbuild-v5.5' of git://git.kernel.org/p..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1416a90ee00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=dd226651cb0f364b
> dashboard link: https://syzkaller.appspot.com/bug?extid=f153bde47a62e0b05f83
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fe9e41e00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1522042ae00000
>
> The bug was bisected to:
>
> commit 65766ee0bf7fe8b3be80e2e1c3ef54ad59b29476
> Author: Takashi Iwai <tiwai@suse.de>
> Date: Fri Nov 9 10:59:45 2018 +0000
>
> ALSA: oss: Use kvzalloc() for local buffer allocations
FYI, this bisection result is bogus; before this commit, the buffer
was allocated via vmalloc and KASAN check was skipped. Now with
kvmalloc(), it goes with kmalloc which has a proper check, and the
problem surfaced since this commit.
The real culprit is a potential buffer overflow in the OSS plugin
chain. I submitted the fix patch now.
Takashi
prev parent reply other threads:[~2019-12-04 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:25 KASAN: slab-out-of-bounds Read in linear_transfer (3) syzbot
2019-12-04 14:50 ` Takashi Iwai [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=s5hlfrskuul.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=syzbot+f153bde47a62e0b05f83@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
/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