All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Xiang Mei <xmei5@asu.edu>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, co+8eacd4fa193b1b28@bugs.sh,
	stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Clamp implicit feedback packet count to URB capacity
Date: Sun, 13 Sep 2026 09:04:19 +0200	[thread overview]
Message-ID: <87mrtlws24.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260912200530.1955491-1-xmei5@asu.edu>

On Sat, 12 Sep 2026 22:05:30 +0200,
Xiang Mei wrote:
> 
> data_ep_set_params() allocates each data URB for exactly u->packets
> isochronous frames, so urb->iso_frame_desc[] has u->packets slots and
> ctx->packets is the driver's only record of that limit. For an implicit
> feedback sink, snd_usb_queue_pending_output_urbs() overwrites it with the
> sync source's packet count, which is calculated independently from the
> capture endpoint's parameters. When that count is larger,
> prepare_playback_urb() and prepare_silent_urb() can write
> iso_frame_desc[] past the allocation; their existing bounds limit payload
> bytes, not the descriptor index.
> 
> The reproducer uses a high-speed UAC2 device declaring bInterval 1 for
> implicit feedback capture (8 packets) and bInterval 4 for playback
> (1 packet). On the first capture completion after the stream starts, it
> accesses seven descriptors spanning 112 bytes beyond the one-packet URB:
> 
>   BUG: KASAN: slab-out-of-bounds in prepare_playback_urb (sound/usb/pcm.c:1560)
>   Write of size 4 at addr ffff88801e696ad0 by task vhci_rx/178
>    prepare_playback_urb (sound/usb/pcm.c:1560)
>    prepare_outbound_urb (sound/usb/endpoint.c:340)
>    snd_usb_queue_pending_output_urbs (sound/usb/endpoint.c:501)
>    snd_complete_urb (sound/usb/endpoint.c:1834)
>    __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657)
>    usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1741)
>    vhci_rx_loop (drivers/usb/usbip/vhci_rx.c:107)
>    kthread (kernel/kthread.c:436)
>   The buggy address belongs to the object at ffff88801e696a00
>    which belongs to the cache kmalloc-256 of size 256
>   The buggy address is located 0 bytes to the right of
>    allocated 208-byte region [ffff88801e696a00, ffff88801e696ad0)
> 
> Record the allocated packet count per endpoint and clamp both the adopted
> count and the packet-size copy to it. Fold the Format Type II delimiter
> into urb_packs before the allocation loop so the recorded limit matches
> every URB.
> 
> Fixes: cf044e441902 ("ALSA: usb-audio: Update the number of packets properly at receiving")
> Reported-by: co+8eacd4fa193b1b28@bugs.sh
> Closes: https://lore.kernel.org/all/22xPn8drvIUtYgVeQnBiNqXuevOTpBAjepLz%40bugs.sh/
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Xiang Mei <xmei5@asu.edu>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-09-13  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 20:05 [PATCH] ALSA: usb-audio: Clamp implicit feedback packet count to URB capacity Xiang Mei
2026-09-13  7:04 ` 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=87mrtlws24.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=co+8eacd4fa193b1b28@bugs.sh \
    --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=xmei5@asu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.