From: Takashi Iwai <tiwai@suse.de>
To: Berk Cem Goksel <berkcgoksel@gmail.com>
Cc: zonque@gmail.com, tiwai@suse.com, perex@perex.cz,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
andreyknvl@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ALSA: caiaq: fix use-after-free and double-free in setup_card()
Date: Tue, 14 Apr 2026 12:56:25 +0200 [thread overview]
Message-ID: <87eckhstd2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260413034941.1131465-2-berkcgoksel@gmail.com>
On Mon, 13 Apr 2026 05:49:40 +0200,
Berk Cem Goksel wrote:
>
> When snd_card_register() fails in setup_card(), snd_card_free() is
> called on the card, but there is no return statement afterwards.
> Execution falls through to snd_usb_caiaq_control_init(cdev), which
> dereferences members of the just-freed card, resulting in a
> use-after-free.
>
> setup_card() is void and init_card() still returns 0 on this path,
> so snd_probe() leaves the freed card pointer in the USB interface's
> private data via usb_set_intfdata(). When the device is later
> disconnected, snd_usb_caiaq_disconnect() calls
> snd_card_free_when_closed() on that same pointer, producing a
> double-free and slab corruption.
>
> Add the missing return so a failed snd_card_register() cleanly
> aborts setup without touching freed memory.
>
> The issue is reachable by any caiaq-compatible USB device whose
> descriptors cause snd_card_register() to fail. It was reproduced
> with raw-gadget + dummy_hcd on 7.0.0-rc5 (arm64, KASAN).
>
> Fixes: 8e3cd08ed8e5 ("[ALSA] caiaq - add control API and more input features")
> Cc: stable@vger.kernel.org
> Cc: Andrey Konovalov <andreyknvl@gmail.com>
> Signed-off-by: Berk Cem Goksel <berkcgoksel@gmail.com>
> ---
> v2:
> - Correct "Fixes:" tag
>
> sound/usb/caiaq/device.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/usb/caiaq/device.c b/sound/usb/caiaq/device.c
> index 3a71bab8a477..d52f3b9a2bac 100644
> --- a/sound/usb/caiaq/device.c
> +++ b/sound/usb/caiaq/device.c
> @@ -369,6 +369,7 @@ static void setup_card(struct snd_usb_caiaqdev *cdev)
> if (ret < 0) {
> dev_err(dev, "snd_card_register() returned %d\n", ret);
> snd_card_free(cdev->chip.card);
> + return;
> }
>
> ret = snd_usb_caiaq_control_init(cdev);
Looking at the code again, this fix doesn't seem sufficing.
And, we have snd_card_free() call in the error case of init_card(),
but setup_card() doesn't give the error back properly.
That said, a proper fix would be to change setup_card() to return the
error, and handle it in init_card(). The place you fixed should
return an error instead of calling snd_card_free() there.
I'm going to cook up a patch.
thanks,
Takashi
next prev parent reply other threads:[~2026-04-14 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 3:49 [PATCH v2 0/2] ALSA: caiaq: fix UAF, double-free, and USB refcount bugs Berk Cem Goksel
2026-04-13 3:49 ` [PATCH v2 1/2] ALSA: caiaq: fix use-after-free and double-free in setup_card() Berk Cem Goksel
2026-04-14 10:56 ` Takashi Iwai [this message]
2026-04-13 3:49 ` [PATCH v2 2/2] ALSA: caiaq: take a reference on the USB device in create_card() Berk Cem Goksel
2026-04-13 5:33 ` Takashi Iwai
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=87eckhstd2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=andreyknvl@gmail.com \
--cc=berkcgoksel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=zonque@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