From: Takashi Iwai <tiwai@suse.de>
To: Hillf Danton <hdanton@sina.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
zonque@gmail.com, LKML <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, linux-usb@vger.kernel.org
Subject: Re: BUG: KASAN: use-after-free in snd_complete_urb+0x109e/0x1740 [snd_usb_audio] (5.11-rc6)
Date: Sat, 06 Feb 2021 09:32:57 +0100 [thread overview]
Message-ID: <s5hk0rl1tqe.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210206081333.7472-1-hdanton@sina.com>
On Sat, 06 Feb 2021 09:13:33 +0100,
Hillf Danton wrote:
>
> On Sat, 6 Feb 2021 Takashi Iwai wrote:
> > > Due to the reconnecting key word mentioned, no fix to
> > > d0f09d1e4a88 ("ALSA: usb-audio: Refactoring endpoint URB deactivation")
> > > will be added.
> > >
> > > What is added is to capture EP_FLAG_STOPPING and remove the one
> > > second wait limit if the reconnecting acts may make it easier to
> > > repro the uaf. The diff is only for idea show.
> >
> > If my understanding is right, this won't change. The problem is
> > rather the lack of this function call itself, i.e. the missing
> > synchronization for the stream stop.
>
> Thanks for taking a look at it.
> >
> > It worked casually in the past because the endpoint resource is
> > released at a later point that is after all streams are really closed.
> > Now it's released earlier and hitting the UAF.
>
> And add it if I dont misread you.
>
> Hillf
>
> --- a/sound/usb/endpoint.c
> +++ b/sound/usb/endpoint.c
> @@ -832,24 +832,14 @@ void snd_usb_endpoint_suspend(struct snd
> */
> static int wait_clear_urbs(struct snd_usb_endpoint *ep)
> {
> - unsigned long end_time = jiffies + msecs_to_jiffies(1000);
> - int alive;
> -
> - if (!test_bit(EP_FLAG_STOPPING, &ep->flags))
> - return 0;
> -
> + WARN_ON_ONCE(!test_bit(EP_FLAG_STOPPING, &ep->flags));
EP_FLAG_STOPPING is normally zero, hence putting a WARN_ON() shows
just a false-positive.
> do {
> - alive = bitmap_weight(&ep->active_mask, ep->nurbs);
> - if (!alive)
> + if (!bitmap_weight(&ep->active_mask, ep->nurbs))
> break;
>
> schedule_timeout_uninterruptible(1);
> - } while (time_before(jiffies, end_time));
> + } while (1);
>
> - if (alive)
> - usb_audio_err(ep->chip,
> - "timeout: still %d active urbs on EP #%x\n",
> - alive, ep->ep_num);
The original report didn't show the error, so it's not about the
timeout. You're likely scratching a wrong surface, I'm afraid.
> clear_bit(EP_FLAG_STOPPING, &ep->flags);
>
> ep->sync_sink = NULL;
> @@ -1433,7 +1423,7 @@ void snd_usb_endpoint_stop(struct snd_us
> WRITE_ONCE(ep->sync_source->sync_sink, NULL);
>
> if (!atomic_dec_return(&ep->running))
> - stop_and_unlink_urbs(ep, false, false);
> + stop_and_unlink_urbs(ep, false, true);
Please don't. This will lead to a sleep-in-atomic Oops.
Takashi
next parent reply other threads:[~2021-02-06 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210206081333.7472-1-hdanton@sina.com>
2021-02-06 8:32 ` Takashi Iwai [this message]
2021-02-05 21:02 BUG: KASAN: use-after-free in snd_complete_urb+0x109e/0x1740 [snd_usb_audio] (5.11-rc6) Mikhail Gavrilov
2021-02-05 22:25 ` Takashi Iwai
[not found] ` <20210206054533.120-1-hdanton@sina.com>
2021-02-06 7:48 ` Takashi Iwai
2021-02-06 8:28 ` Takashi Iwai
2021-02-06 12:19 ` 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=s5hk0rl1tqe.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.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;
as well as URLs for NNTP newsgroup(s).