From: Takashi Iwai <tiwai@suse.de>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [alsa-devel] usb/sound: use-after-free in __uac_clock_find_source
Date: Tue, 21 Nov 2017 17:27:29 +0100 [thread overview]
Message-ID: <s5hd14bvbpq.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAAeHK+wuqb4nCFWTriGsiT4y8dOdQM4B+wtDLYh5Z3mjwjKy=A@mail.gmail.com>
On Tue, 21 Nov 2017 14:52:00 +0100,
Andrey Konovalov wrote:
>
> Hi!
>
> I've got the following report while fuzzing the kernel with syzkaller.
>
> On commit e1d1ea549b57790a3d8cf6300e6ef86118d692a3 (4.15-rc1).
>
> This actually looks more like an out-of-bounds with large offset than
> a use-after-free due to unrelated alloc and free stack traces.
Yes, similar as the previous report, but at this time, it's about the
clock selector stuff. Will provide the fix patch, too.
thanks,
Takashi
prev parent reply other threads:[~2017-11-21 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 13:52 Andrey Konovalov
2017-11-21 16:27 ` 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=s5hd14bvbpq.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=syzkaller@googlegroups.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
all inboxes | Powered by JetHome®