linux-kernel - Re: [PATCH -next v2] ALSA: timer: Fix use-after-free problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hh7ctkzi8.wl-tiwai@suse.de>
Date:   Wed, 03 Nov 2021 16:52:31 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Wang Wensheng <wangwensheng4@...wei.com>
Cc:     <perex@...ex.cz>, <tiwai@...e.com>, <broonie@...nel.org>,
        <joe@...ches.com>, <alsa-devel@...a-project.org>,
        <linux-kernel@...r.kernel.org>, <rui.xiang@...wei.com>
Subject: Re: [PATCH -next v2] ALSA: timer: Fix use-after-free problem

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@...wei.com>
> Suggested-by: Takashi Iwai <tiwai@...e.de>

Thanks, applied now.


Takashi