public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavitra Jha <jhapavitra98@gmail.com>
Cc: linux-usb@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: MAX3420 UDC: out-of-bounds read/write via unvalidated wIndex in USB SETUP packet
Date: Sun, 12 Apr 2026 07:05:39 +0200	[thread overview]
Message-ID: <2026041211-prevalent-busload-0453@gregkh> (raw)
In-Reply-To: <CALFbBidSiJTD2zdczQ1_mxv8Xm9Pqspnz8LDppHp2hudkLSoxw@mail.gmail.com>

On Sat, Apr 11, 2026 at 11:28:08PM +0530, Pavitra Jha wrote:
> Hello,
> 
> I am reporting an out-of-bounds read and write in the MAX3420 USB
> Device Controller driver. The issue arises from using a
> host-controlled wIndex field from a USB SETUP packet as a direct index
> into a fixed-size endpoint array without validating that the index is
> within bounds.
> 
> The driver handles USB control requests originating from an external
> USB host and therefore must treat all request fields as untrusted.

Did you look in the mailing list archives for this driver?  This has
been discussed in the past, most recently:
	https://lore.kernel.org/r/20260121203944.1898-2-qikeyu2017@gmail.com

Please get this hardware and validate that this even actually can
happen, as last time around, it was stated that it could not due to how
the hardware worked.  If that is incorrect, we'll be glad to take the
change, but that needs to actually be tested, not just attempted with a
fake device in qemu.

thanks,

greg k-h

      parent reply	other threads:[~2026-04-12  5:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 17:58 MAX3420 UDC: out-of-bounds read/write via unvalidated wIndex in USB SETUP packet Pavitra Jha
2026-04-11 18:00 ` [PATCH] usb: gadget: udc: max3420: validate endpoint index before array access Pavitra Jha
2026-04-12  5:05 ` Greg KH [this message]

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=2026041211-prevalent-busload-0453@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jhapavitra98@gmail.com \
    --cc=linux-kernel@vger.kernel.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