From: Johan Hovold <johan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jiale Yao <yaojiale02@163.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: serial: fix slab out-of-bounds read in interrupt URB callback
Date: Mon, 13 Jul 2026 12:02:14 +0200 [thread overview]
Message-ID: <alS3pmrV-FwEsVvA@hovoldconsulting.com> (raw)
In-Reply-To: <2026071325-onward-sabotage-13e8@gregkh>
On Mon, Jul 13, 2026 at 08:30:38AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Jul 13, 2026 at 01:00:12AM +0800, Jiale Yao wrote:
> > @@ -2672,6 +2672,13 @@ static void option_instat_callback(struct urb *urb)
> > dev_dbg(dev, "%s: NULL req_pkt\n", __func__);
> > return;
> > }
> > +
> > + if (urb->actual_length < sizeof(struct usb_ctrlrequest) + 1) {
> > + dev_dbg(dev, "%s: short interrupt transfer: %d bytes\n",
> > + __func__, urb->actual_length);
> > + return;
> > + }
>
> Close, shouldn't this be rewritten to be:
>
> if (urb->actual_length < sizeof(*req_pkt) + 1) {
> dev_dbg(dev, "%s: short packet %u\n", __func__,
> urb->actual_length);
>
> As that's the structure you need to care about instead?
The load uses sizeof(struct usb_ctrlrequest) currently so I think it's
fine to use that in the length check as well.
But looking at this again, the check should be split in two: one for the
struct usb_ctrlrequest header and one for the modem signal state (inside
the conditional).
Johan
next prev parent reply other threads:[~2026-07-13 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 17:00 [PATCH] usb: serial: fix slab out-of-bounds read in interrupt URB callback Jiale Yao
2026-07-13 6:30 ` Greg KH
2026-07-13 10:02 ` Johan Hovold [this message]
2026-07-13 10:44 ` Oliver Neukum
2026-07-13 13:55 ` Johan Hovold
2026-07-13 9:56 ` Johan Hovold
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=alS3pmrV-FwEsVvA@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=yaojiale02@163.com \
/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