From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
To: Frode Isaksen <fisaksen@baylibre.com>, Thinh.Nguyen@synopsys.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
Frode Isaksen <frode@meta.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: dwc3: gadget: check that event count does not exceed event buffer length
Date: Tue, 1 Apr 2025 11:13:22 +0530 [thread overview]
Message-ID: <0767d38d-179a-4c5e-9dfe-fef847d1354d@oss.qualcomm.com> (raw)
In-Reply-To: <20250328104930.2179123-1-fisaksen@baylibre.com>
On 3/28/2025 4:14 PM, Frode Isaksen wrote:
> From: Frode Isaksen <frode@meta.com>
>
> The event count is read from register DWC3_GEVNTCOUNT.
> There is a check for the count being zero, but not for exceeding the
> event buffer length.
> Check that event count does not exceed event buffer length,
> avoiding an out-of-bounds access when memcpy'ing the event.
> Crash log:
> Unable to handle kernel paging request at virtual address ffffffc0129be000
> pc : __memcpy+0x114/0x180
> lr : dwc3_check_event_buf+0xec/0x348
> x3 : 0000000000000030 x2 : 000000000000dfc4
> x1 : ffffffc0129be000 x0 : ffffff87aad60080
> Call trace:
> __memcpy+0x114/0x180
> dwc3_interrupt+0x24/0x34
>
> Signed-off-by: Frode Isaksen <frode@meta.com>
> Fixes: ebbb2d59398f ("usb: dwc3: gadget: use evt->cache for processing events")
> Cc: stable@vger.kernel.org
> ---
> v1 -> v2: Added Fixes and Cc tag.
>
> This bug was discovered, tested and fixed (no more crashes seen) on Meta Quest 3 device.
> Also tested on T.I. AM62x board.
>
> drivers/usb/dwc3/gadget.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index 63fef4a1a498..548e112167f3 100644
> --- a/drivers/usb/dwc3/gadget.c
> +++ b/drivers/usb/dwc3/gadget.c
> @@ -4564,7 +4564,7 @@ static irqreturn_t dwc3_check_event_buf(struct dwc3_event_buffer *evt)
>
> count = dwc3_readl(dwc->regs, DWC3_GEVNTCOUNT(0));
> count &= DWC3_GEVNTCOUNT_MASK;
> - if (!count)
> + if (!count || count > evt->length)
> return IRQ_NONE;
>
> evt->count = count;
I did see this issue previously ([1] on 5.10) on SAR2130 (upstreamed
recently). Can you help check if the issue is same on your end if you
can reproduce it easily. Thinh also provided some debug pointers to
check suspecting it to be a HW issue.
As per the comments from Thinh, he suggested to add a error log as well
when this happens [2].
[1]:
https://lore.kernel.org/all/20230521100330.22478-1-quic_kriskura@quicinc.com/
[2]:
https://lore.kernel.org/all/20230525001822.ane3zcyyifj2kuwx@synopsys.com/
Regards,
Krishna,
next prev parent reply other threads:[~2025-04-01 5:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 10:44 [PATCH v2] usb: dwc3: gadget: check that event count does not exceed event buffer length Frode Isaksen
2025-04-01 5:43 ` Krishna Kurapati [this message]
2025-04-01 12:08 ` Frode Isaksen
2025-04-01 12:26 ` Krishna Kurapati
2025-04-01 23:36 ` Thinh Nguyen
2025-04-02 4:42 ` Krishna Kurapati
2025-04-02 7:50 ` Frode Isaksen
2025-04-02 22:22 ` Thinh Nguyen
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 12:53 Frode Isaksen
2025-04-01 13:49 ` Greg KH
2025-04-01 23:43 ` Thinh Nguyen
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=0767d38d-179a-4c5e-9dfe-fef847d1354d@oss.qualcomm.com \
--to=krishna.kurapati@oss.qualcomm.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=fisaksen@baylibre.com \
--cc=frode@meta.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@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