* [PATCH] usb: usbtmc: reject a short READ_STATUS_BYTE control transfer
@ 2026-11-19 8:39 Hyunjung Ko
2026-11-19 8:45 ` sashiko-bot
0 siblings, 1 reply; 2+ messages in thread
From: Hyunjung Ko @ 2026-11-19 8:39 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Guido Kiener, linux-usb, linux-kernel, stable, Hyunjung Ko
usbtmc_get_stb() asks the device for three bytes of the READ_STATUS_BYTE
response into a kmalloc()'d buffer and only checks that usb_control_msg()
did not fail:
buffer = kmalloc(8, GFP_KERNEL);
...
rv = usb_control_msg(..., buffer, 0x03, USB_CTRL_GET_TIMEOUT);
if (rv < 0)
goto exit;
usb_control_msg() returns the number of bytes actually transferred,
which a device is free to make shorter than the three that were
requested. When the interface has no interrupt-in endpoint the status
byte is then taken straight from the third byte:
*stb = buffer[2];
and the caller hands it to user space with put_user() from
USBTMC488_IOCTL_READ_STB and USBTMC_IOCTL_GET_SRQ_STB. A device that
answers with one or two bytes - with the first byte set to
USBTMC_STATUS_SUCCESS so the status check passes - therefore leaks one
byte of uninitialised kmalloc memory to user space. Both conditions are
under the device's control, since it also decides whether to expose an
interrupt-in endpoint.
The same leak was fixed once before in this driver: usbtmc_ioctl_request()
bounds its copy_to_user() to the number of bytes usb_control_msg() reported
instead of the number requested. usbtmc_get_stb() cannot be fixed that way
because it reads a fixed offset, so reject the transfer unless all three
bytes arrived, matching what usbtmc488_ioctl_simple() already does for its
own one-byte request.
The check is not limited to the branch that reads buffer[2]: buffer[0] is
consumed on both paths, so a short response leaves the status check itself
reading uninitialised memory. USBTMC-USB488 4.3.1 requires the three-byte
response, so a device that sends fewer is not conforming either way.
Signed-off-by: Hyunjung Ko <hj351016@gmail.com>
Cc: stable@vger.kernel.org
---
drivers/usb/class/usbtmc.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
index 51cd9320a736..c5b91a446a72 100644
--- a/drivers/usb/class/usbtmc.c
+++ b/drivers/usb/class/usbtmc.c
@@ -506,6 +506,10 @@ static int usbtmc_get_stb(struct usbtmc_file_data *file_data, __u8 *stb)
if (rv < 0) {
dev_err(dev, "stb usb_control_msg returned %d\n", rv);
goto exit;
+ } else if (rv != 3) {
+ dev_warn(dev, "stb usb_control_msg returned %d\n", rv);
+ rv = -EIO;
+ goto exit;
}
if (buffer[0] != USBTMC_STATUS_SUCCESS) {
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] usb: usbtmc: reject a short READ_STATUS_BYTE control transfer
2026-11-19 8:39 [PATCH] usb: usbtmc: reject a short READ_STATUS_BYTE control transfer Hyunjung Ko
@ 2026-11-19 8:45 ` sashiko-bot
0 siblings, 0 replies; 2+ messages in thread
From: sashiko-bot @ 2026-11-19 8:45 UTC (permalink / raw)
To: Hyunjung Ko; +Cc: linux-usb
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] usb: usbtmc: missing Fixes trailer and wrong ioctl name in
commit message
--
commit 65820c8baf3e3185b7eb9f2281ee331492c9b001
Author: Hyunjung Ko <hj351016@gmail.com>
> usb: usbtmc: reject a short READ_STATUS_BYTE control transfer
>
> usbtmc_get_stb() asks the device for three bytes of the READ_STATUS_BYTE
> response into a kmalloc()'d buffer and only checks that usb_control_msg()
> did not fail:
>
> buffer = kmalloc(8, GFP_KERNEL);
> ...
> rv = usb_control_msg(..., buffer, 0x03, USB_CTRL_GET_TIMEOUT);
> if (rv < 0)
> goto exit;
>
> usb_control_msg() returns the number of bytes actually transferred,
> which a device is free to make shorter than the three that were
> requested. When the interface has no interrupt-in endpoint the status
> byte is then taken straight from the third byte:
>
> *stb = buffer[2];
>
> and the caller hands it to user space with put_user() from
> USBTMC488_IOCTL_READ_STB and USBTMC_IOCTL_GET_SRQ_STB. A device that
> answers with one or two bytes - with the first byte set to
> USBTMC_STATUS_SUCCESS so the status check passes - therefore leaks one
> byte of uninitialised kmalloc memory to user space. Both conditions are
> under the device's control, since it also decides whether to expose an
> interrupt-in endpoint.
>
> The same leak was fixed once before in this driver: usbtmc_ioctl_request()
> bounds its copy_to_user() to the number of bytes usb_control_msg() reported
> instead of the number requested. usbtmc_get_stb() cannot be fixed that way
> because it reads a fixed offset, so reject the transfer unless all three
> bytes arrived, matching what usbtmc488_ioctl_simple() already does for its
> own one-byte request.
>
> The check is not limited to the branch that reads buffer[2]: buffer[0] is
> consumed on both paths, so a short response leaves the status check itself
> reading uninitialised memory. USBTMC-USB488 4.3.1 requires the three-byte
> response, so a device that sends fewer is not conforming either way.
>
> Signed-off-by: Hyunjung Ko <hj351016@gmail.com>
> Cc: stable@vger.kernel.org
[Severity: Low]
Should this bug fix include a Fixes tag for the commit that introduced the
unchecked three-byte READ_STATUS_BYTE control transfer:
Fixes: dbf3e7f654c0 ("Implement an ioctl to support the USMTMC-USB488 READ_STATUS_BYTE operation.")
Also, the commit message mentions USBTMC_IOCTL_GET_SRQ_STB as the second
caller of usbtmc_get_stb(), but in usbtmc_ioctl() the second caller is
USBTMC_IOCTL_GET_STB (USBTMC_IOCTL_GET_SRQ_STB calls
usbtmc_ioctl_get_srq_stb() instead).
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261119083959.1599898-1-hj351016@gmail.com?part=1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-19 8:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-19 8:39 [PATCH] usb: usbtmc: reject a short READ_STATUS_BYTE control transfer Hyunjung Ko
2026-11-19 8:45 ` sashiko-bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox