Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Norbert Szetei <norbert@doyensec.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	tiwai@suse.de, perex@perex.cz
Subject: Re: [PATCH] ALSA: seq: close a re-opened queue timer in the destructor
Date: Tue, 14 Jul 2026 11:10:47 +0200	[thread overview]
Message-ID: <87jyqyym08.wl-tiwai@suse.de> (raw)
In-Reply-To: <422FDB81-2A68-47C7-A22D-2D3301E2E86D@doyensec.com>

On Tue, 14 Jul 2026 10:29:23 +0200,
Norbert Szetei wrote:
> 
> queue_delete() closes the queue timer, then frees it. snd_seq_timer_close()
> clears q->timer->timeri. snd_use_lock_sync() then drains borrowers, and
> snd_seq_timer_delete() frees q->timer.
> 
> A borrower can re-open the timer inside that window. A SET_QUEUE_CLIENT
> that took a queueptr() use_lock reference before the queue was unlinked
> runs snd_seq_timer_open() after the close. Open refuses re-open only while
> timeri is set, and the close just cleared it, so it re-opens timeri.
> 
> snd_seq_timer_delete() does not close that instance. Its snd_seq_timer_stop()
> is a no-op, because running was cleared first. So it frees q->timer with the
> instance still live. The queue is freed next.
> 
> The instance stays on the global timer with callback_data pointing at the
> freed queue. A non-owner START on the unlocked queue arms it. The next tick
> derefs the freed queue in snd_seq_timer_interrupt().
> 
> Reachable by an unprivileged user with access to /dev/snd/seq. No CAP and
> no queue ownership required.
> 
> Close any lingering instance in the destructor. There, ->timeri can no
> longer change: the queue is unlinked and all use_lock borrowers have
> drained, so no snd_seq_queue_use() can re-open it. Close it before clearing
> q->timer. snd_timer_close() waits for any in-flight snd_seq_timer_interrupt()
> to finish, and that callback still reads q->timer (via snd_seq_check_queue()),
> so q->timer must stay valid until it drains.
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Norbert Szetei <norbert@doyensec.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-07-14  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  8:29 [PATCH] ALSA: seq: close a re-opened queue timer in the destructor Norbert Szetei
2026-07-14  9:10 ` 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=87jyqyym08.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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