From: Greg KH <gregkh@linuxfoundation.org>
To: Taegu Ha <hataegu0826@gmail.com>
Cc: linux-usb@vger.kernel.org, kees@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_uac1_legacy: validate control request size
Date: Wed, 1 Apr 2026 13:30:45 +0200 [thread overview]
Message-ID: <2026040124-unheated-opponent-3c56@gregkh> (raw)
In-Reply-To: <20260401104611.3375330-1-hataegu0826@gmail.com>
On Wed, Apr 01, 2026 at 07:46:11PM +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>
> ---
> drivers/usb/gadget/function/f_uac1_legacy.c | 19 ++++++++++++++++---
> 1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/f_uac1_legacy.c b/drivers/usb/gadget/function/f_uac1_legacy.c
> index a0c953a99727..6d6fe5db99f5 100644
> --- a/drivers/usb/gadget/function/f_uac1_legacy.c
> +++ b/drivers/usb/gadget/function/f_uac1_legacy.c
> @@ -11,6 +11,7 @@
> #include <linux/module.h>
> #include <linux/device.h>
> #include <linux/atomic.h>
> +#include <asm/unaligned.h>
>
> #include "u_uac1_legacy.h"
>
> @@ -370,9 +371,21 @@ static void f_audio_complete(struct usb_ep *ep, struct usb_request *req)
> 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));
> + struct usb_audio_control *con = audio->set_con;
> +
> + if ((con->type == UAC_FU_MUTE && req->actual != sizeof(u8)) ||
> + (con->type == UAC_FU_VOLUME && req->actual != sizeof(__le16)) ||
> + (con->type != UAC_FU_MUTE && con->type != UAC_FU_VOLUME)) {
> + usb_ep_set_halt(ep);
> + audio->set_con = NULL;
> + break;
> + }
> +
> + if (con->type == UAC_FU_MUTE)
> + data = *(u8 *)req->buf;
> + else
> + data = get_unaligned_le16(req->buf);
Very cool, thanks for finding and fixing this. But there is a bit of a
coding style issue in that big if check, AND it's hard to follow, how
about doing something like this instead (totally untested and not even
compiled:
struct usb_audio_control *con = audio->set_con;
u8 type = con->type;
bool valid_request = false;
switch (type) {
case: UAC_FU_MUTE:
if (req->actual == sizeof(__u8)) {
memcpy(&data, req->buf, sizeof(__u8));
valid_request = true;
}
break;
case UAC_FU_VOLUME:
if (req->actual == sizeof(__le16) {
memcpy(&data, req->buf, sizeof(__le16));
valid_request = true;
}
break;
}
if (valid_request)
con->set(con, audio->set_cmd, data);
else
usb_ep_set_halt(ep);
audio->set_con = NULL;
}
Does that make it easier to read? I don't know, maybe not, your call,
but this way the memcpy of a constant size should be equalivant to your
direct cast if the compiler is sane, right?
And as this is a __le16 value, should we be doing some endian conversion
somewhere?
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-01 11:30 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 [this message]
2026-04-01 15:15 ` [PATCH v2] " Taegu Ha
2026-04-01 18:28 ` Greg KH
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=2026040124-unheated-opponent-3c56@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hataegu0826@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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