From: Zhang Xiaolei <zxl434815272@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: brgl@kernel.org, warthog618@gmail.com,
linux-kernel@vger.kernel.org,
Zhang Xiaolei <zxl434815272@gmail.com>
Subject: [PATCH] tools: gpio: fix buffer overflow and add bounds check
Date: Mon, 4 May 2026 03:00:16 +0800 [thread overview]
Message-ID: <20260503190016.13439-1-zxl434815272@gmail.com> (raw)
Replace strcpy() with strncpy() to avoid potential buffer overflow
in req.consumer. Also add validation for num_lines to prevent
out-of-bounds access to req.offsets.
Fix incorrect ioctl name in error message.
Signed-off-by: Zhang Xiaolei <zxl434815272@gmail.com>
---
tools/gpio/gpio-utils.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/tools/gpio/gpio-utils.c b/tools/gpio/gpio-utils.c
index 4096bcd511d1..1afd9dff2bed 100644
--- a/tools/gpio/gpio-utils.c
+++ b/tools/gpio/gpio-utils.c
@@ -65,11 +65,15 @@ int gpiotools_request_line(const char *device_name, unsigned int *lines,
int i;
int ret;
+ if (!device_name || !lines || !config || !consumer ||
+ num_lines == 0 || num_lines > GPIO_V2_LINES_MAX)
+ return -EINVAL;
+
ret = asprintf(&chrdev_name, "/dev/%s", device_name);
if (ret < 0)
return -ENOMEM;
- fd = open(chrdev_name, 0);
+ fd = open(chrdev_name, O_RDONLY);
if (fd == -1) {
ret = -errno;
fprintf(stderr, "Failed to open %s, %s\n",
@@ -78,27 +82,29 @@ int gpiotools_request_line(const char *device_name, unsigned int *lines,
}
memset(&req, 0, sizeof(req));
+
for (i = 0; i < num_lines; i++)
req.offsets[i] = lines[i];
req.config = *config;
- strcpy(req.consumer, consumer);
+ strncpy(req.consumer, consumer, sizeof(req.consumer) - 1);
+ req.consumer[sizeof(req.consumer) - 1] = '\0';
req.num_lines = num_lines;
ret = ioctl(fd, GPIO_V2_GET_LINE_IOCTL, &req);
if (ret == -1) {
ret = -errno;
fprintf(stderr, "Failed to issue %s (%d), %s\n",
- "GPIO_GET_LINE_IOCTL", ret, strerror(errno));
+ "GPIO_V2_GET_LINE_IOCTL", ret, strerror(errno));
}
if (close(fd) == -1)
perror("Failed to close GPIO character device file");
+
exit_free_name:
free(chrdev_name);
return ret < 0 ? ret : req.fd;
}
-
/**
* gpiotools_set_values() - Set the value of gpio(s)
* @fd: The fd returned by
--
2.54.0
next reply other threads:[~2026-05-03 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 19:00 Zhang Xiaolei [this message]
2026-05-03 20:56 ` [PATCH] tools: gpio: fix buffer overflow and add bounds check Maxwell Doose
2026-05-04 5:46 ` 007
2026-05-04 5:55 ` 007
2026-05-04 7:50 ` [PATCH v2 1/3] tools: gpio: use strscpy() for consumer name Zhang Xiaolei
2026-05-04 7:50 ` [PATCH v2 2/3] tools: gpio: validate arguments in gpiotools_request_line Zhang Xiaolei
2026-05-04 16:13 ` Maxwell Doose
2026-05-04 7:50 ` [PATCH v2 3/3] tools: gpio: fix ioctl name in error message Zhang Xiaolei
2026-05-04 17:47 ` Maxwell Doose
2026-05-04 12:45 ` [PATCH v2 1/3] tools: gpio: use strscpy() for consumer name David Laight
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=20260503190016.13439-1-zxl434815272@gmail.com \
--to=zxl434815272@gmail.com \
--cc=brgl@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@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