From: Takashi Iwai <tiwai@suse.de>
To: HyeongJun An <sammiee5311@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: seq: Don't leak the extension cell pointer in the bounce payload
Date: Tue, 11 Aug 2026 18:22:40 +0200 [thread overview]
Message-ID: <87mrusaapb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260811131835.3837024-1-sammiee5311@gmail.com>
On Tue, 11 Aug 2026 15:18:35 +0200,
HyeongJun An wrote:
>
> The bounce_error_event() embeds the failed event in the bounce payload
> by pointing data.ext.ptr at it. When that event is a queued
> variable-length event, its own data.ext.ptr holds the address of its
> first extension cell, put there by snd_seq_event_dup(). The payload
> goes out verbatim through snd_seq_expand_var_event(), so the address
> reaches userspace.
>
> That is the same address commit 705dd6dcbc0e ("ALSA: seq: Clear
> variable event pointer on read") removed from the event header. The
> read path still clears it there, just above the call that expands the
> payload.
>
> Embed a sanitised copy instead, treated exactly as snd_seq_read()
> treats the header. A stack copy is enough because delivery is
> synchronous and snd_seq_event_dup() copies before returning.
>
> An unprivileged client reaches this by setting SNDRV_SEQ_FILTER_BOUNCE,
> queueing a variable-length event to a port that does not exist and
> reading the bounce back. Eight bytes on 64-bit, from its own pool.
>
> Fixes: efc86691e4d8 ("ALSA: seq: Fix kernel heap address leak in bounce_error_event()")
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: HyeongJun An <sammiee5311@gmail.com>
Applied now to for-next branch now.
> ---
> Unrelated, and not part of the change: the payload does not match struct
> snd_seq_event_bounce in include/uapi/sound/asequencer.h - the err field is
> not sent. Nothing regressed, since the kernel never produced the event
> before efc86691e4d8. I can fix that separately if you want it.
Any further fix would be appreciated.
thanks,
Takashi
prev parent reply other threads:[~2026-08-11 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:18 [PATCH] ALSA: seq: Don't leak the extension cell pointer in the bounce payload HyeongJun An
2026-08-11 16:22 ` 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=87mrusaapb.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sammiee5311@gmail.com \
--cc=tiwai@suse.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