[<prev] [next>] [day] [month] [year] [list]
Message-ID: <YuAggxK2DA72FSZh@kroah.com>
Date: Tue, 26 Jul 2022 19:12:35 +0200
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Andy Guo (郭卫斌) <guoweibin@...pur.com>
Cc: "b-liu@...com" <b-liu@...com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: musb: Fix musb_gadget.c rxstate may cause
request->buf overflow problems
On Tue, Jul 26, 2022 at 01:59:48AM +0000, Andy Guo (郭卫斌) wrote:
> when the rxstate function executes the 'goto buffer_aint_mapped' code
> branch, it will always copy the fifocnt bytes data to request->buf,
> which may cause request->buf out of bounds. for Ethernet-over-USB will
> cause skb_over_panic when a packet larger than mtu is recived.
>
> Fix it by add the length check :
> fifocnt = min_t(unsigned, request->length - request->actual, fifocnt);
>
> Signed-off-by: guoweibin < <mailto:guoweibin@...pur.com>
> guoweibin@...pur.com>
> ---
> drivers/usb/musb/musb_gadget.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
> index 51274b87f46c..4ad5a1f31d7e 100644
> --- a/drivers/usb/musb/musb_gadget.c
> +++ b/drivers/usb/musb/musb_gadget.c
> @@ -760,6 +760,7 @@ static void rxstate(struct musb *musb, struct
> musb_request *req)
> musb_writew(epio, MUSB_RXCSR, csr);
>
> buffer_aint_mapped:
> + fifo_count = min_t(unsigned, request->length - request->actual,
> fifo_count);
> musb_read_fifo(musb_ep->hw_ep, fifo_count, (u8 *)
> (request->buf + request->actual));
> request->actual += fifo_count;
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
and can not be applied. Please read the file,
Documentation/email-clients.txt in order to fix this.
- Your patch was attached, please place it inline so that it can be
applied directly from the email message itself.
- It looks like you did not use your "real" name for the patch on either
the Signed-off-by: line, or the From: line (both of which have to
match). Please read the kernel file, Documentation/SubmittingPatches
for how to do this correctly.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists