From: Takashi Iwai <tiwai@suse.de>
To: John Keeping <john@metanate.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ALSA: rawmidi: Fix potential UAF from sequencer destruction
Date: Wed, 29 Sep 2021 17:28:57 +0200 [thread overview]
Message-ID: <s5hv92jl7t2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210929161758.49ce947f.john@metanate.com>
On Wed, 29 Sep 2021 17:17:58 +0200,
John Keeping wrote:
>
> On Wed, 29 Sep 2021 16:51:47 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
>
> > On Wed, 29 Sep 2021 13:36:20 +0200,
> > John Keeping wrote:
> > >
> > > If the sequencer device outlives the rawmidi device, then
> > > snd_rawmidi_dev_seq_free() will run after release_rawmidi_device() has
> > > freed the snd_rawmidi structure.
> > >
> > > This can easily be reproduced with CONFIG_DEBUG_KOBJECT_RELEASE.
> > >
> > > Keep a reference to the rawmidi device until the sequencer has been
> > > destroyed in order to avoid this.
> > >
> > > Signed-off-by: John Keeping <john@metanate.com>
> >
> > Thanks for the patch. I wonder, though, how this could be triggered.
> > Is this the case where the connected sequencer device is being used
> > while the sound card gets released? Or is it something else?
>
> I'm not sure if it's possible to trigger via the ALSA API; I haven't
> found a route that can trigger it, but that doesn't mean there isn't
> one :-)
>
> Mostly this is useful to make CONFIG_DEBUG_KOBJECT_RELEASE cleaner.
Hm, then could you check whether the patch below papers over it
instead?
thanks,
Takashi
--- a/sound/core/seq/seq_ports.c
+++ b/sound/core/seq/seq_ports.c
@@ -415,11 +415,16 @@ static int subscribe_port(struct snd_seq_client *client,
grp->count--;
}
}
- if (err >= 0 && send_ack && client->type == USER_CLIENT)
+ if (err < 0)
+ return err;
+
+ if (send_ack && client->type == USER_CLIENT)
snd_seq_client_notify_subscription(port->addr.client, port->addr.port,
info, SNDRV_SEQ_EVENT_PORT_SUBSCRIBED);
+ else if (client->type == KERNEL_CLIENT)
+ get_device(&client->data.kernel.card->card_dev);
- return err;
+ return 0;
}
static int unsubscribe_port(struct snd_seq_client *client,
@@ -439,6 +444,8 @@ static int unsubscribe_port(struct snd_seq_client *client,
snd_seq_client_notify_subscription(port->addr.client, port->addr.port,
info, SNDRV_SEQ_EVENT_PORT_UNSUBSCRIBED);
module_put(port->owner);
+ if (client->type == KERNEL_CLIENT)
+ snd_card_unref(client->data.kernel.card);
return err;
}
next prev parent reply other threads:[~2021-09-29 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 11:36 John Keeping
2021-09-29 14:51 ` Takashi Iwai
2021-09-29 15:17 ` John Keeping
2021-09-29 15:28 ` Takashi Iwai [this message]
2021-09-29 16:56 ` John Keeping
2021-09-30 6:31 ` Takashi Iwai
2021-09-30 6:55 ` Takashi Iwai
2021-09-30 10:27 ` John Keeping
2021-09-30 11:40 ` 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=s5hv92jl7t2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=john@metanate.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®