From: Takashi Iwai <tiwai@suse.de>
To: Berk Cem Goksel <berkcgoksel@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
stable@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: 6fire: fix use-after-free on disconnect
Date: Fri, 10 Apr 2026 08:35:34 +0200 [thread overview]
Message-ID: <87se93gw5l.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260410051341.1069716-1-berkcgoksel@gmail.com>
On Fri, 10 Apr 2026 07:13:41 +0200,
Berk Cem Goksel wrote:
>
> In usb6fire_chip_abort(), the chip struct is allocated as the card's
> private data (via snd_card_new with sizeof(struct sfire_chip)). When
> snd_card_free_when_closed() is called and no file handles are open, the
> card and embedded chip are freed synchronously. The subsequent
> chip->card = NULL write then hits freed slab memory.
>
> Call trace:
> usb6fire_chip_abort sound/usb/6fire/chip.c:59 [inline]
> usb6fire_chip_disconnect+0x348/0x358 sound/usb/6fire/chip.c:182
> usb_unbind_interface+0x1a8/0x88c drivers/usb/core/driver.c:458
> ...
> hub_event+0x1a04/0x4518 drivers/usb/core/hub.c:5953
>
> Fix by moving the card lifecycle out of usb6fire_chip_abort() and into
> usb6fire_chip_disconnect(). The card pointer is saved in a local
> before any teardown, snd_card_disconnect() is called first to prevent
> new opens, URBs are aborted while chip is still valid, and
> snd_card_free_when_closed() is called last so chip is never accessed
> after the card may be freed.
>
> Fixes: a0810c3d6dd2 ("ALSA: 6fire: Release resources at card release")
> Cc: stable@vger.kernel.org
> Cc: Andrey Konovalov <andreyknvl@gmail.com>
> Signed-off-by: Berk Cem Goksel <berkcgoksel@gmail.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-04-10 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 5:13 [PATCH] ALSA: 6fire: fix use-after-free on disconnect Berk Cem Goksel
2026-04-10 6:35 ` 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=87se93gw5l.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 \
/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