From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Maoyi Xie <maoyixie.tju@gmail.com>
Cc: Lixu Zhang <lixu.zhang@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: ljca: bound bank_num in ljca_enumerate_gpio()
Date: Thu, 18 Jun 2026 09:56:20 +0300 [thread overview]
Message-ID: <ajOWlN0RbjosG_Me@kekkonen.localdomain> (raw)
In-Reply-To: <178176358875.3352358.6059116660356914900@maoyixie.com>
Hi Maoyi,
Thanks for the patch.
On Thu, Jun 18, 2026 at 02:19:48PM +0800, Maoyi Xie wrote:
> ljca_enumerate_gpio() reads desc->bank_num from the device and loops
> valid_pin[i] = get_unaligned_le32(...) for i < bank_num. valid_pin[]
> holds only LJCA_MAX_GPIO_NUM / 32 = 2 entries.
>
> Two checks run before the loop. The reply length must match
> struct_size(desc, bank_desc, bank_num). The product
> pins_per_bank * bank_num must not exceed LJCA_MAX_GPIO_NUM. Neither one
> bounds bank_num against the size of valid_pin[]. The reply is capped at
> LJCA_MAX_PAYLOAD_SIZE (60) bytes, so the struct_size check limits
> bank_num to 9. A device that reports bank_num 9 with pins_per_bank 7
> still passes both checks. gpio_num is 63 and the reply is 56 bytes. The
> loop then writes nine u32 into the two entry array and overruns
> valid_pin[] on the stack.
>
> A broken or malicious LJCA device can therefore overflow the stack.
> Reject a bank_num that does not fit valid_pin[].
>
> Fixes: acd6199f195d ("usb: Add support for Intel LJCA device")
> Cc: stable@vger.kernel.org
> Signed-off-by: Maoyi Xie <maoyixie.tju@gmail.com>
> ---
> drivers/usb/misc/usb-ljca.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/misc/usb-ljca.c b/drivers/usb/misc/usb-ljca.c
> index c60121faa3da..a1876c05b7c2 100644
> --- a/drivers/usb/misc/usb-ljca.c
> +++ b/drivers/usb/misc/usb-ljca.c
> @@ -596,6 +596,9 @@ static int ljca_enumerate_gpio(struct ljca_adapter *adap)
> if (gpio_num > LJCA_MAX_GPIO_NUM)
> return -EINVAL;
>
> + if (desc->bank_num > ARRAY_SIZE(valid_pin))
> + return -EINVAL;
> +
This certainly does fix the problem but it looks like the code somehow
appears to assume desc->pins_per_bank is always 32. I guess that's ok as
it's been working in the past.
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> /* construct platform data */
> gpio_info = kzalloc_obj(*gpio_info);
> if (!gpio_info)
--
Kind regards,
Sakari Ailus
prev parent reply other threads:[~2026-06-18 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 6:19 Maoyi Xie
2026-06-18 6:56 ` Sakari Ailus [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=ajOWlN0RbjosG_Me@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=maoyixie.tju@gmail.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
all inboxes | Powered by JetHome®