From: Sergio Perez Gonzalez <sperezglz@gmail.com>
To: gregkh@linuxfoundation.org, michal.simek@amd.com
Cc: Sergio Perez Gonzalez <sperezglz@gmail.com>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, shuah@kernel.org
Subject: [PATCH] usb: gadget: udc-xilinx: validate ep number before indexing rambase[]
Date: Fri, 27 Jun 2025 00:01:22 -0600 [thread overview]
Message-ID: <20250627060125.176663-1-sperezglz@gmail.com> (raw)
Issue flagged by coverity. The size of the rambase array is 8,
usb_enpoint_num() can return 0 to 15, prevent out of bounds reads.
Link: https://scan7.scan.coverity.com/#/project-view/53936/11354?selectedIssue=1644635
Signed-off-by: Sergio Perez Gonzalez <sperezglz@gmail.com>
---
drivers/usb/gadget/udc/udc-xilinx.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/gadget/udc/udc-xilinx.c b/drivers/usb/gadget/udc/udc-xilinx.c
index 8d803a612bb1..0c3714de2e3b 100644
--- a/drivers/usb/gadget/udc/udc-xilinx.c
+++ b/drivers/usb/gadget/udc/udc-xilinx.c
@@ -814,6 +814,12 @@ static int __xudc_ep_enable(struct xusb_ep *ep,
ep->is_in = ((desc->bEndpointAddress & USB_DIR_IN) != 0);
/* Bit 3...0:endpoint number */
ep->epnumber = usb_endpoint_num(desc);
+ if (ep->epnumber >= XUSB_MAX_ENDPOINTS) {
+ dev_dbg(udc->dev, "bad endpoint index %d: only 0 to %d supported\n",
+ ep->epnumber, (XUSB_MAX_ENDPOINTS - 1));
+ return -EINVAL;
+ }
+
ep->desc = desc;
ep->ep_usb.desc = desc;
tmp = usb_endpoint_type(desc);
--
2.43.0
next reply other threads:[~2025-06-27 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 6:01 Sergio Perez Gonzalez [this message]
2025-06-28 15:04 ` [PATCH] usb: gadget: udc-xilinx: validate ep number before indexing rambase[] Greg KH
2025-06-30 20:20 ` Sergio Pérez
2025-07-01 8:43 ` Greg KH
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=20250627060125.176663-1-sperezglz@gmail.com \
--to=sperezglz@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=shuah@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