From: Takashi Iwai <tiwai@suse.de>
To: Benoit Sevens <bsevens@google.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Lianqin Hu <hulianqin@vivo.com>,
Manuel Barrio Linares <mbarriolinares@gmail.com>,
wangdicheng <wangdicheng@kylinos.cn>,
linux-sound@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy devices
Date: Sun, 17 Nov 2024 15:00:24 +0100 [thread overview]
Message-ID: <87h686q7t3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20241115130833.1077260-1-bsevens@google.com>
On Fri, 15 Nov 2024 14:08:33 +0100,
Benoit Sevens wrote:
>
> A bogus devices can provide a bNumConfigurations value that exceeds the
> initial value used in usb_get_configuration for allocating dev->config.
>
> This can lead to out-of-bounds accesses later, e.g. in
> usb_destroy_configuration.
It'd be more helpful if you can elaborate how it can happen; the code
you touched doesn't call much stuff, just send a boot sequence and
reset the configuration. Yet your patch tries to overwrite a
usb_device field, which isn't really a task for the driver side.
thanks,
Takashi
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@kernel.org
> Signed-off-by: Benoit Sevens <bsevens@google.com>
> ---
> sound/usb/quirks.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
> index c5fd180357d1..970d36d13ad8 100644
> --- a/sound/usb/quirks.c
> +++ b/sound/usb/quirks.c
> @@ -555,6 +555,7 @@ int snd_usb_create_quirk(struct snd_usb_audio *chip,
> static int snd_usb_extigy_boot_quirk(struct usb_device *dev, struct usb_interface *intf)
> {
> struct usb_host_config *config = dev->actconfig;
> + int num_configs;
> int err;
>
> if (le16_to_cpu(get_cfg_desc(config)->wTotalLength) == EXTIGY_FIRMWARE_SIZE_OLD ||
> @@ -565,8 +566,11 @@ static int snd_usb_extigy_boot_quirk(struct usb_device *dev, struct usb_interfac
> 0x10, 0x43, 0x0001, 0x000a, NULL, 0);
> if (err < 0)
> dev_dbg(&dev->dev, "error sending boot message: %d\n", err);
> + num_configs = dev->descriptor.bNumConfigurations;
> err = usb_get_descriptor(dev, USB_DT_DEVICE, 0,
> &dev->descriptor, sizeof(dev->descriptor));
> + if (dev->descriptor.bNumConfigurations > num_configs)
> + dev->descriptor.bNumConfigurations = num_configs;
> config = dev->actconfig;
> if (err < 0)
> dev_dbg(&dev->dev, "error usb_get_descriptor: %d\n", err);
> --
> 2.47.0.338.g60cca15819-goog
>
next prev parent reply other threads:[~2024-11-17 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 13:08 [PATCH] ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy devices Benoit Sevens
2024-11-17 14:00 ` Takashi Iwai [this message]
2024-11-18 10:07 ` Benoît Sevens
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=87h686q7t3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bsevens@google.com \
--cc=hulianqin@vivo.com \
--cc=linux-sound@vger.kernel.org \
--cc=mbarriolinares@gmail.com \
--cc=perex@perex.cz \
--cc=stable@kernel.org \
--cc=tiwai@suse.com \
--cc=wangdicheng@kylinos.cn \
/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