From: Takashi Iwai <tiwai@suse.de>
To: Norbert Szetei <norbert@doyensec.com>
Cc: linux-sound@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] ALSA: timer: Clear SNDRV_TIMER_IFLG_DEAD once the close completes
Date: Sun, 26 Jul 2026 16:12:04 +0200 [thread overview]
Message-ID: <87ldaxalhn.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA41AA48-75BF-45E9-A36D-3A5D2F124F60@doyensec.com>
On Sun, 26 Jul 2026 10:01:45 +0200,
Norbert Szetei wrote:
>
> snd_timer_close_locked() marks an instance with SNDRV_TIMER_IFLG_DEAD
> and returns early when the flag is already set, but the flag is never
> cleared again. A completed close ends in remove_slave_links(), which
> leaves timeri->timer NULL, so a second close is already harmless through
> the timer == NULL path; the early return can only be reached by an
> instance that was opened again in between. For such an instance the
> close unlinks nothing, so snd_timer_instance_free() frees an object that
> is still on timer->open_list_head, still on snd_timer_master_list if it
> was opened with a slave key, still owns any adopted slaves, and still
> holds its timer and module references.
>
> snd_seq_timer_open() reopens an instance exactly like that: it retries
> its fallback open on the same object after a failure that has already
> run snd_timer_close_locked() internally. An unprivileged user with
> access to /dev/snd/timer and /dev/snd/seq can force that failure, since
> snd_timer_check_master() returns -EBUSY when a pending slave matches the
> new master's (slave_class, slave_id) key and the target timer has
> reached max_instances, and SNDRV_TIMER_IOCTL_SELECT with dev_class =
> SNDRV_TIMER_CLASS_SLAVE keeps the caller-supplied dev_sclass, so a
> sequencer queue's key can be forged. The freed instance is afterwards
> dereferenced by any further snd_timer_open() on that timer, by
> snd_timer_check_slave(), and by /proc/asound/timers, which faults on the
> stale ti->owner pointer.
>
> The flag only has to be visible while the close is in progress, which is
> all its other users need. Clear it in remove_slave_links(), under the
> same timer->lock that sets it, once the instance is off every list.
>
> Fixes: da3039e91d1f ("ALSA: timer: Forcibly close timer instances at closing")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Norbert Szetei <norbert@doyensec.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-07-26 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 8:01 [PATCH] ALSA: timer: Clear SNDRV_TIMER_IFLG_DEAD once the close completes Norbert Szetei
2026-07-26 14:12 ` 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=87ldaxalhn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=perex@perex.cz \
/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