From: Greg KH <gregkh@linuxfoundation.org>
To: Taegu Ha <hataegu0826@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: gadget: f_uac1_legacy: validate control request size
Date: Wed, 1 Apr 2026 20:28:42 +0200 [thread overview]
Message-ID: <2026040144-gratitude-haven-f28a@gregkh> (raw)
In-Reply-To: <20260401151539.3441000-1-hataegu0826@gmail.com>
On Thu, Apr 02, 2026 at 12:15:39AM +0900, Taegu Ha wrote:
> f_audio_complete() copies req->length bytes into a 4-byte stack
> variable:
>
> u32 data = 0;
> memcpy(&data, req->buf, req->length);
>
> req->length is derived from the host-controlled USB request path,
> which can lead to a stack out-of-bounds write.
>
> Validate req->actual against the expected payload size for the
> supported control selectors and decode only the expected amount
> of data.
>
> This avoids copying a host-influenced length into a fixed-size
> stack object.
>
> Signed-off-by: Taegu Ha <hataegu0826@gmail.com>
>
> Changes in v2:
> - rewrite the validation logic into a switch on control type
> - use constant-size memcpy() for fixed-size payloads
> - convert the volume payload with le16_to_cpu()
>
> Build-tested: not tested, build environment not prepared
As you found and tested your previous change, can you please test this
one to verify it solves the issue?
>
> ---
> drivers/usb/gadget/function/f_uac1_legacy.c | 47 ++++++++++++++++-----
> 1 file changed, 37 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/f_uac1_legacy.c b/drivers/usb/gadget/function/f_uac1_legacy.c
> index a0c953a99727..00cc7161db66 100644
> --- a/drivers/usb/gadget/function/f_uac1_legacy.c
> +++ b/drivers/usb/gadget/function/f_uac1_legacy.c
> @@ -360,19 +360,46 @@ static int f_audio_out_ep_complete(struct usb_ep *ep, struct usb_request *req)
> static void f_audio_complete(struct usb_ep *ep, struct usb_request *req)
> {
> struct f_audio *audio = req->context;
> - int status = req->status;
> - u32 data = 0;
> struct usb_ep *out_ep = audio->out_ep;
>
> - switch (status) {
> -
> - case 0: /* normal completion? */
> - if (ep == out_ep)
> + switch (req->status) {
> + case 0:
> + if (ep == out_ep) {
> f_audio_out_ep_complete(ep, req);
> - else if (audio->set_con) {
> - memcpy(&data, req->buf, req->length);
> - audio->set_con->set(audio->set_con, audio->set_cmd,
> - le16_to_cpu(data));
> + } else if (audio->set_con) {
> + struct usb_audio_control *con = audio->set_con;
> + u8 type = con->type;
> + u32 data = 0;
No need to set this to 0 ahead of time, right?
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-01 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 10:46 [PATCH] usb: gadget: f_uac1_legacy: validate control request size Taegu Ha
2026-04-01 11:30 ` Greg KH
2026-04-01 15:15 ` [PATCH v2] " Taegu Ha
2026-04-01 18:28 ` Greg KH [this message]
2026-04-01 19:13 ` [PATCH v3] " Taegu Ha
2026-04-12 9:49 ` [PATCH] " kernel test robot
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=2026040144-gratitude-haven-f28a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hataegu0826@gmail.com \
--cc=linux-usb@vger.kernel.org \
/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