From: pip-izony <eeodqql09@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Seungjin Bae <eeodqql09@gmail.com>,
Kyungtae Kim <Kyungtae.Kim@dartmouth.edu>,
Alan Stern <stern@rowland.harvard.edu>,
Kees Cook <kees@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
David Mosberger <davidm@egauge.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 1/2] usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()
Date: Sun, 17 May 2026 15:03:07 -0400 [thread overview]
Message-ID: <20260517190308.1876316-1-eeodqql09@gmail.com> (raw)
In-Reply-To: <20260517000145.1868817-2-eeodqql09@gmail.com>
From: Seungjin Bae <eeodqql09@gmail.com>
The `max3421_hub_control()` function handles USB hub class requests
to the virtual root hub. In the `default` branches of both the
`ClearPortFeature` and `SetPortFeature` switch statements, it modifies
`max3421_hcd->port_status` by left shifting 1 by the request's `value`
parameter. However, it does not validate whether this shift will exceed
the width of `port_status`.
So if a malicious userspace task with access to the root hub via
/dev/bus/usb/.../001 issues a USBDEVFS_CONTROL ioctl with `wValue`
greater than or equal to 32, the left shift operation invokes
shift-out-of-bounds undefined behavior. This results in arbitrary
bit corruption of `port_status`, including the normally-immutable
change bits, which can bypass internal state checks and confuse the
hub status.
Fix this by rejecting requests whose `value` exceeds the shift width
before performing the shift.
Fixes: 2d53139f3162 ("Add support for using a MAX3421E chip as a host driver.")
Signed-off-by: Seungjin Bae <eeodqql09@gmail.com>
---
v1 -> v2: Restored a paragraph in the commit message that was truncated.
v2 -> v3: No functional changes; reorganized as part of a 2-patch series.
drivers/usb/host/max3421-hcd.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/host/max3421-hcd.c b/drivers/usb/host/max3421-hcd.c
index 0e17c988d36a..3d6b351dcb1a 100644
--- a/drivers/usb/host/max3421-hcd.c
+++ b/drivers/usb/host/max3421-hcd.c
@@ -1694,6 +1694,8 @@ max3421_hub_control(struct usb_hcd *hcd, u16 type_req, u16 value, u16 index,
!pdata->vbus_active_level);
fallthrough;
default:
+ if (value >= 32)
+ goto error;
max3421_hcd->port_status &= ~(1 << value);
}
break;
@@ -1747,6 +1749,8 @@ max3421_hub_control(struct usb_hcd *hcd, u16 type_req, u16 value, u16 index,
max3421_reset_port(hcd);
fallthrough;
default:
+ if (value >= 32)
+ goto error;
if ((max3421_hcd->port_status & USB_PORT_STAT_POWER)
!= 0)
max3421_hcd->port_status |= (1 << value);
--
2.43.0
next prev parent reply other threads:[~2026-05-17 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 0:01 [PATCH] " pip-izony
2026-05-17 0:07 ` [PATCH v2] " pip-izony
2026-05-17 1:15 ` Alan Stern
2026-05-17 18:11 ` Seungjin Bae
2026-05-17 5:49 ` [PATCH] " Greg Kroah-Hartman
2026-05-17 18:19 ` Seungjin Bae
2026-05-18 5:19 ` Greg Kroah-Hartman
2026-05-17 19:03 ` pip-izony [this message]
2026-05-17 19:03 ` [PATCH v3 2/2] usb: host: max3421: Reject hub port requests for non-existent ports pip-izony
2026-05-18 21:54 ` Alan Stern
2026-05-18 22:37 ` Seungjin Bae
2026-05-18 22:49 ` [PATCH v4 1/2] usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() pip-izony
2026-05-18 22:49 ` [PATCH v4 2/2] usb: host: max3421: Reject hub port requests for non-existent ports pip-izony
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=20260517190308.1876316-1-eeodqql09@gmail.com \
--to=eeodqql09@gmail.com \
--cc=Kyungtae.Kim@dartmouth.edu \
--cc=dan.carpenter@linaro.org \
--cc=davidm@egauge.net \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®