From: Greg KH <gregkh@linuxfoundation.org>
To: "Benoît Sevens" <bsevens@google.com>
Cc: stable@vger.kernel.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 5.10.y] ALSA: usb-audio: Fix out of bounds reads when finding clock sources
Date: Thu, 5 Dec 2024 10:48:51 +0100 [thread overview]
Message-ID: <2024120526-jawless-robust-ea3f@gregkh> (raw)
In-Reply-To: <20241205092925.922510-1-bsevens@google.com>
On Thu, Dec 05, 2024 at 09:29:25AM +0000, Benoît Sevens wrote:
> From: Takashi Iwai <tiwai@suse.de>
>
> The current USB-audio driver code doesn't check bLength of each
> descriptor at traversing for clock descriptors. That is, when a
> device provides a bogus descriptor with a shorter bLength, the driver
> might hit out-of-bounds reads.
>
> For addressing it, this patch adds sanity checks to the validator
> functions for the clock descriptor traversal. When the descriptor
> length is shorter than expected, it's skipped in the loop.
>
> For the clock source and clock multiplier descriptors, we can just
> check bLength against the sizeof() of each descriptor type.
> OTOH, the clock selector descriptor of UAC2 and UAC3 has an array
> of bNrInPins elements and two more fields at its tail, hence those
> have to be checked in addition to the sizeof() check.
>
> Reported-by: Benoît Sevens <bsevens@google.com>
> Cc: <stable@vger.kernel.org>
> Link: https://lore.kernel.org/20241121140613.3651-1-bsevens@google.com
> Link: https://patch.msgid.link/20241125144629.20757-1-tiwai@suse.de
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> (cherry picked from commit a3dd4d63eeb452cfb064a13862fb376ab108f6a6)
You did _MUCH_ more than just cherry picking this. Please document your
changes somehow, this is much different from the original commit.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-05 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 9:29 [PATCH 5.10.y] ALSA: usb-audio: Fix out of bounds reads when finding clock sources Benoît Sevens
2024-12-05 9:48 ` Greg KH [this message]
2024-12-05 13:34 ` Sasha Levin
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=2024120526-jawless-robust-ea3f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bsevens@google.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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.