From: Vincent Mailhol <mailhol@kernel.org>
To: James Gao <jamesgao5@outlook.com>, mkl@pengutronix.de
Cc: linux-can@vger.kernel.org, s.grosjean@peak-system.fr,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] can: peak_usb: Add bounds check for USB channel index
Date: Fri, 15 May 2026 13:34:14 +0200 [thread overview]
Message-ID: <e6ad1a37-2c78-44cd-9004-bdadf73b7042@kernel.org> (raw)
In-Reply-To: <TYCPR01MB856782BAA657447E5EDDDC1FF0062@TYCPR01MB8567.jpnprd01.prod.outlook.com>
On 13/05/2026 at 11:51, James Gao wrote:
> The channel control index ctrl_idx is derived from rx->len which comes
> directly from a device USB payload. The mask 0x0f allows values 0-15,
> but the array size of usb_if->dev[] is only 2. Values 2-15 cause heap
> out-of-bounds read, eventually causing kernel panic in the IRQ context.
>
> Add bounds checking for ctrl_idx before the array access in both
> pcan_usb_pro_handle_canmsg() and pcan_usb_pro_handle_error().
>
> Fixes: d8a199355f8f ("can: usb: PEAK-System Technik PCAN-USB Pro specific part")
> Signed-off-by: James Gao <jamesgao5@outlook.com>
> ---
>
> Hi Marc,
> Thanks for the review for v1. Since this is not a security bug I have
> moved the discussion to public mail list. Changes in v2:
> - Use ARRAY_SIZE(usb_if->dev) instead of PCAN_USBPRO_CHANNEL_COUNT
> - Use -EINVAL instead of -ENOMEM
> - Add newline between variable declaration and bounds check
> - Wrap commit message
>
> drivers/net/can/usb/peak_usb/pcan_usb_pro.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/net/can/usb/peak_usb/pcan_usb_pro.c b/drivers/net/can/usb/peak_usb/pcan_usb_pro.c
> index 4bfa8d0fbb32..5b1e3501cfb8 100644
> --- a/drivers/net/can/usb/peak_usb/pcan_usb_pro.c
> +++ b/drivers/net/can/usb/peak_usb/pcan_usb_pro.c
> @@ -534,6 +534,10 @@ static int pcan_usb_pro_handle_canmsg(struct pcan_usb_pro_interface *usb_if,
> struct pcan_usb_pro_rxmsg *rx)
> {
> const unsigned int ctrl_idx = (rx->len >> 4) & 0x0f;
> +
> + if (ctrl_idx >= ARRAY_SIZE(usb_if->dev))
> + return -EINVAL;
Please don't tangle declarations and expressions.
const unsigned int ctrl_idx = (rx->len >> 4) & 0x0f;
struct peak_usb_device *dev;
struct net_device *netdev;
struct can_frame *can_frame;
struct sk_buff *skb;
struct skb_shared_hwtstamps *hwts;
if (ctrl_idx >= ARRAY_SIZE(usb_if->dev))
return -EINVAL;
dev = usb_if->dev[ctrl_idx];
netdev = dev->netdev;
Aside from that, looks OK.
> struct peak_usb_device *dev = usb_if->dev[ctrl_idx];
> struct net_device *netdev = dev->netdev;
> struct can_frame *can_frame;
> @@ -573,6 +577,10 @@ static int pcan_usb_pro_handle_error(struct pcan_usb_pro_interface *usb_if,
> {
> const u16 raw_status = le16_to_cpu(er->status);
> const unsigned int ctrl_idx = (er->channel >> 4) & 0x0f;
> +
> + if (ctrl_idx >= ARRAY_SIZE(usb_if->dev))
> + return -EINVAL;
Same comment as above.
> struct peak_usb_device *dev = usb_if->dev[ctrl_idx];
> struct net_device *netdev = dev->netdev;
> struct can_frame *can_frame;
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2026-05-15 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 9:51 [PATCH v2] can: peak_usb: Add bounds check for USB channel index James Gao
2026-05-15 10:04 ` Stéphane Grosjean
2026-05-15 11:34 ` Vincent Mailhol [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=e6ad1a37-2c78-44cd-9004-bdadf73b7042@kernel.org \
--to=mailhol@kernel.org \
--cc=jamesgao5@outlook.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.grosjean@peak-system.fr \
/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