From: Johan Hovold <johan@kernel.org>
To: Jiale Yao <yaojiale02@163.com>
Cc: gregkh@linuxfoundation.org, 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 11:56:40 +0200 [thread overview]
Message-ID: <alS2WOB1L2bXDuYy@hovoldconsulting.com> (raw)
In-Reply-To: <20260712170012.3503601-1-yaojiale02@163.com>
On Mon, Jul 13, 2026 at 01:00:12AM +0800, Jiale Yao wrote:
> The interrupt URB buffer is allocated in setup_port_interrupt_in() based
> on the endpoint's wMaxPacketSize:
>
> buffer_size = usb_endpoint_maxp(epd);
> port->interrupt_in_buffer = kmalloc(buffer_size, GFP_KERNEL);
>
> When a USB device declares wMaxPacketSize = 8 on its interrupt IN
> endpoint, the buffer is allocated from kmalloc-8 cache (exactly 8 bytes).
>
> If the device sends a short packet (actual_length < wMaxPacketSize),
> the URB completes with status == 0 and the callback proceeds to read:
>
> data[sizeof(struct usb_ctrlrequest)]
>
> which evaluates to data[8], accessing 1 byte beyond the allocated 8-byte
> buffer. This results in a slab out-of-bounds read.
>
> Fix this by adding a bounds check before accessing data[8], ensuring that
> the actual length is sufficient to contain a full USB control request
> header.
>
> Signed-off-by: Jiale Yao <yaojiale02@163.com>
This looks correct, but how was this issue found and how was the patch
created?
If you used an LLM you need to document this in the commit message, see:
Documentation/process/generated-content.rst
Documentation/process/coding-assistants.rst
Johan
prev parent reply other threads:[~2026-07-13 9:56 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
2026-07-13 10:44 ` Oliver Neukum
2026-07-13 13:55 ` Johan Hovold
2026-07-13 9:56 ` Johan Hovold [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=alS2WOB1L2bXDuYy@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