From: Takashi Iwai <tiwai@suse.de>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
jjzuming@gmail.com
Subject: Re: [PATCH] ALSA: aloop: Keep the timer source alive until card release
Date: Mon, 19 Oct 2026 20:06:08 +0200 [thread overview]
Message-ID: <87tsmhimzz.wl-tiwai@suse.de> (raw)
In-Reply-To: <pm-pmb-71a33a26d68356e3ade7-v1-108d86919c5c92fe1ea8@gmail.com>
On Mon, 19 Oct 2026 11:06:13 +0200,
Cen Zhang wrote:
>
> The timer_source string must remain valid while PCM opens can select
> and parse it. loopback_set_timer_source() allocates the string with
> parent-device devres, which can release it while the card is still
> registered.
>
> A successful nonempty proc replacement after snd_card_register() adds
> the string allocation after trigger_card_free. Unbinding the platform
> device while snd_aloop remains loaded releases devres in reverse order.
> An open for an unused cable can run after the string is freed and before
> the card-free action disconnects the card:
>
> Device unbind PCM open
> devres_release_all()
> free replacement string
> snd_pcm_open()
> snd_card_file_add()
> loopback_open()
> loopback_snd_timer_open()
> loopback_parse_timer_id()
> trigger_card_free()
> snd_card_free()
> snd_card_disconnect()
>
> The parser can then read freed memory. KASAN has reported a one-byte
> use-after-free read in strchr() from loopback_snd_timer_open(). The
> cable_lock mutex serializes explicit replacements with opens, but
> implicit devres release does not take it. The card and module references
> held by PCM open do not retain this separate devres allocation.
>
> Use kstrdup() and release the current string from card->private_free.
> PCM admission already retains the card until each file is removed, and
> card disconnect drains proc callbacks before final card release. This
> keeps the string alive across admitted PCM opens and preserves the
> cable_lock serialization of replacements. Install the callback before
> the initial allocation so probe failures also release the string.
>
> Fixes: b072e65aadd6 ("ALSA: aloop: Allocate resources with device-managed APIs")
> Signed-off-by: Cen Zhang <zzzccc427@gmail.com>
> Assisted-by: LLM
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-19 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 9:06 Cen Zhang
2026-10-19 18: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=87tsmhimzz.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=baijiaju1990@gmail.com \
--cc=jjzuming@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zzzccc427@gmail.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®