From: Takashi Iwai <tiwai@suse.de>
To: Wang Wensheng <wangwensheng4@huawei.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>, <broonie@kernel.org>,
<joe@perches.com>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <rui.xiang@huawei.com>
Subject: Re: [PATCH -next v2] ALSA: timer: Fix use-after-free problem
Date: Wed, 03 Nov 2021 17:06:41 +0100 [thread overview]
Message-ID: <s5ha6ilkyum.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hh7ctkzi8.wl-tiwai@suse.de>
On Wed, 03 Nov 2021 16:52:31 +0100,
Takashi Iwai wrote:
>
> On Wed, 03 Nov 2021 04:35:17 +0100,
> Wang Wensheng wrote:
> >
> > When the timer instance was add into ack_list but was not currently in
> > process, the user could stop it via snd_timer_stop1() without delete it
> > from the ack_list. Then the user could free the timer instance and when
> > it was actually processed UAF occurred.
> >
> > This issue could be reproduced via testcase snd_timer01 in ltp - running
> > several instances of that testcase at the same time.
> >
> > What I actually met was that the ack_list of the timer broken and the
> > kernel went into deadloop with irqoff. That could be detected by
> > hardlockup detector on board or when we run it on qemu, we could use gdb
> > to dump the ack_list when the console has no response.
> >
> > To fix this issue, we delete the timer instance from ack_list and
> > active_list unconditionally in snd_timer_stop1().
> >
> > Signed-off-by: Wang Wensheng <wangwensheng4@huawei.com>
> > Suggested-by: Takashi Iwai <tiwai@suse.de>
>
> Thanks, applied now.
BTW, while reviewing the patch, I noticed that we have also the
similar code path for a slave timer instance that has the same kind of
linked list entries. I'll submit the corresponding fix patch.
Takashi
prev parent reply other threads:[~2021-11-03 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 3:35 Wang Wensheng
2021-11-03 15:52 ` Takashi Iwai
2021-11-03 16:06 ` 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=s5ha6ilkyum.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rui.xiang@huawei.com \
--cc=tiwai@suse.com \
--cc=wangwensheng4@huawei.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®