From: Joas Antonio dos Santos via B4 Relay <devnull+joasantonio108.gmail.com@kernel.org>
To: mkl@pengutronix.de, mailhol@kernel.org, frank.jungclaus@esd.eu,
socketcan@esd.eu, joasantonio108@gmail.com
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH 1/2] can: esd_usb: limit the number of nets reported by the device
Date: Tue, 10 Nov 2026 03:56:28 +0000 [thread overview]
Message-ID: <20261110-esd-usb-validate-v1-1-7ee499b4926d@gmail.com> (raw)
In-Reply-To: <20261110-esd-usb-validate-v1-0-7ee499b4926d@gmail.com>
From: Joas Antonio dos Santos <joasantonio108@gmail.com>
esd_usb_probe() takes the number of CAN nets from the version reply
sent by the device and uses it unchecked as the loop bound for
esd_usb_probe_one_net(), which stores the new private data pointer in
dev->nets[index]. The nets array only has ESD_USB_MAX_NETS (2)
entries, while the device controlled u8 can be up to 255.
A device that reports more than two nets makes the driver write
pointers past the end of the array, first over the following members
of struct esd_usb and then beyond the end of the allocation. The
loops in esd_usb_read_bulk_callback(), unlink_all_urbs() and
esd_usb_disconnect() read dev->nets[] with the same bound.
A malicious USB device can use this to corrupt kernel heap memory
just by being plugged in.
Clamp the count to the size of the array.
Found by LLM-assisted source review.
Fixes: 96d8e90382dc ("can: Add driver for esd CAN-USB/2 device")
Cc: stable@vger.kernel.org
Signed-off-by: Joas Antonio dos Santos <joasantonio108@gmail.com>
---
drivers/net/can/usb/esd_usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/can/usb/esd_usb.c b/drivers/net/can/usb/esd_usb.c
index f41d4a0d140f..f26a8780686f 100644
--- a/drivers/net/can/usb/esd_usb.c
+++ b/drivers/net/can/usb/esd_usb.c
@@ -1343,7 +1343,7 @@ static int esd_usb_probe(struct usb_interface *intf,
goto free_msg;
}
- dev->net_count = (int)msg->version_reply.nets;
+ dev->net_count = min_t(int, msg->version_reply.nets, ESD_USB_MAX_NETS);
dev->version = le32_to_cpu(msg->version_reply.version);
if (device_create_file(&intf->dev, &dev_attr_firmware))
--
2.43.0
next prev parent reply other threads:[~2026-11-10 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 3:56 [PATCH 0/2] can: esd_usb: validate data received from " Joas Antonio dos Santos via B4 Relay
2026-11-10 3:56 ` Joas Antonio dos Santos via B4 Relay [this message]
2026-11-10 3:56 ` [PATCH 2/2] can: esd_usb: validate the message length in the rx path Joas Antonio dos Santos via B4 Relay
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=20261110-esd-usb-validate-v1-1-7ee499b4926d@gmail.com \
--to=devnull+joasantonio108.gmail.com@kernel.org \
--cc=frank.jungclaus@esd.eu \
--cc=joasantonio108@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@esd.eu \
--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
all inboxes | Powered by JetHome®