From: Omer Cohen <nevergfx1@gmail.com>
To: tiwai@suse.de, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, security@kernel.org,
Omer Cohen <nevergfx1@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH 2/6] ALSA: compress: fix buffer leak on set_params driver failure
Date: Fri, 26 Jun 2026 16:47:05 +0300 [thread overview]
Message-ID: <20260626134709.27883-3-nevergfx1@gmail.com> (raw)
In-Reply-To: <20260626134709.27883-1-nevergfx1@gmail.com>
snd_compr_set_params() calls snd_compr_allocate_buffer() which stores
the new buffer pointer in runtime->buffer, then calls
ops->set_params(). If the driver callback fails, the function returns
the error but runtime->buffer already points to the new allocation.
On a subsequent set_params retry, snd_compr_allocate_buffer() overwrites
runtime->buffer with a fresh allocation without freeing the previous
one, leaking kernel memory.
An unprivileged user with access to a compress offload device can
trigger this repeatedly to exhaust kernel memory.
Fix by saving the old buffer state before allocation and restoring it
if the driver callback fails.
Fixes: b21c60a4edd2 ("ALSA: core: add support for compress_offload")
Cc: stable@vger.kernel.org
Reported-by: Omer Cohen <nevergfx1@gmail.com>
Signed-off-by: Omer Cohen <nevergfx1@gmail.com>
---
sound/core/compress_offload.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/sound/core/compress_offload.c b/sound/core/compress_offload.c
index fd63d219bf86..XXXXXXXXXXXX 100644
--- a/sound/core/compress_offload.c
+++ b/sound/core/compress_offload.c
@@ -665,14 +665,28 @@ snd_compr_set_params(struct snd_compr_stream *stream, unsigned long arg)
if (retval)
return retval;
+ void *old_buffer = stream->runtime->buffer;
+ size_t old_size = stream->runtime->buffer_size;
+ unsigned int old_frag_size = stream->runtime->fragment_size;
+ unsigned int old_fragments = stream->runtime->fragments;
+
retval = snd_compr_allocate_buffer(stream, params);
if (retval)
return -ENOMEM;
retval = stream->ops->set_params(stream, params);
- if (retval)
+ if (retval) {
+ /* Restore old buffer to avoid leak on retry.
+ * Free the newly allocated one if it differs.
+ */
+ if (stream->runtime->buffer != old_buffer &&
+ !stream->runtime->dma_buffer_p)
+ kfree(stream->runtime->buffer);
+ stream->runtime->buffer = old_buffer;
+ stream->runtime->buffer_size = old_size;
+ stream->runtime->fragment_size = old_frag_size;
+ stream->runtime->fragments = old_fragments;
return retval;
+ }
if (stream->next_track)
return retval;
--
2.43.0
next prev parent reply other threads:[~2026-06-26 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260626134709.27883-1-nevergfx1@gmail.com>
2026-06-26 13:47 ` [PATCH 1/6] ALSA: compress: remove illegal state mutation in poll() Omer Cohen
2026-06-26 13:47 ` Omer Cohen [this message]
2026-06-26 13:47 ` [PATCH 3/6] ALSA: timer: fix lockless tu->tread read in snd_timer_user_read() Omer Cohen
2026-06-26 13:47 ` [PATCH 4/6] ALSA: timer: copy queue entries to local buffer before copy_to_user Omer Cohen
2026-06-26 13:47 ` [PATCH 5/6] ALSA: pcm: use locked state read in snd_pcm_drop() Omer Cohen
2026-06-26 13:47 ` [PATCH 6/6] ALSA: rawmidi: propagate resize_runtime_buffer() error in input_params Omer Cohen
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=20260626134709.27883-3-nevergfx1@gmail.com \
--to=nevergfx1@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=security@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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