From: Oliver Neukum <oneukum@suse.com>
To: Jay Vadayath <jkrshnmenon@gmail.com>,
gregkh@linuxfoundation.org, johan@kernel.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Lukas Dresel <lukas@artiphishell.com>
Subject: Re: [PATCH] USB: serial: sierra: fix slab out-of-bounds read in sierra_instat_callback
Date: Tue, 14 Jul 2026 20:25:27 +0200 [thread overview]
Message-ID: <4e7abb00-f0ab-4008-a0bf-5ccd90102aca@suse.com> (raw)
In-Reply-To: <20260714181142.10976-1-jkrshnmenon@gmail.com>
On 14.07.26 20:11, Jay Vadayath wrote:
> The interrupt-in URB buffer is allocated based on the endpoint's
> wMaxPacketSize. A device declaring wMaxPacketSize == 8 gets an 8-byte
> buffer from kmalloc-8. When such a device delivers a short packet,
> sierra_instat_callback() still dereferences transfer_buffer as struct
> usb_ctrlrequest and reads a further byte at data[sizeof(*req_pkt)], one
> byte past the end of the allocation.
>
> Reject the URB when fewer than sizeof(struct usb_ctrlrequest) + 1 bytes
> were received.
>
> Cc: stable@vger.kernel.org
> Reported-by: Jay Vadayath <jkrshnmenon@gmail.com>
> Reported-by: Lukas Dresel <lukas@artiphishell.com>
> Signed-off-by: Jay Vadayath <jkrshnmenon@gmail.com>
Nacked-by: Oliver Neukum <oneukum@suse.com>
> +
> + if (urb->actual_length < sizeof(struct usb_ctrlrequest) + 1) {
> + dev_dbg(&port->dev, "%s: short interrupt transfer: %d bytes\n",
> + __func__, urb->actual_length);
> + return;
> + }
I am sorry, but you cannot do this. Not here.
> +
> if ((req_pkt->bRequestType == 0xA1) &&
> (req_pkt->bRequest == 0x20)) {
This is the test you need to check how long the reply needs to be.
If we look at the full evaluation of the package from the driver we have:
}
if ((req_pkt->bRequestType == 0xA1) &&
(req_pkt->bRequest == 0x20)) {
int old_dcd_state;
unsigned char signals = *((unsigned char *)
urb->transfer_buffer +
sizeof(struct usb_ctrlrequest));
dev_dbg(&port->dev, "%s: signal x%x\n", __func__,
signals);
old_dcd_state = portdata->dcd_state;
portdata->cts_state = 1;
portdata->dcd_state = ((signals & 0x01) ? 1 : 0);
portdata->dsr_state = ((signals & 0x02) ? 1 : 0);
portdata->ri_state = ((signals & 0x08) ? 1 : 0);
if (old_dcd_state && !portdata->dcd_state)
tty_port_tty_hangup(&port->port, true);
} else {
dev_dbg(&port->dev, "%s: type %x req %x\n",
__func__, req_pkt->bRequestType,
req_pkt->bRequest);
}
In this branch:
if ((req_pkt->bRequestType == 0xA1) &&
(req_pkt->bRequest == 0x20)) {
replies must be at least sizeof(struct usb_ctrlrequest) + 1 long.
But in the else branch a length of sizeof(struct usb_ctrlrequest) will do,
because they do not evaluate the signal.
In other words, you stop processing messages if a message the driver does not
care about, but is valid under the specification arrives. That breaks the driver.
Regards
Oliver
next prev parent reply other threads:[~2026-07-14 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://lore.kernel.org/all/2026071453-reminder-ageless-dcea@gregkh/>
2026-07-14 18:11 ` Jay Vadayath
2026-07-14 18:25 ` Oliver Neukum [this message]
2026-07-15 7:21 ` 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=4e7abb00-f0ab-4008-a0bf-5ccd90102aca@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkrshnmenon@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@artiphishell.com \
--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
Powered by JetHome