From: "Nuno Sá" <noname.nuno@gmail.com>
To: Markus Burri <markus.burri@mt.com>, linux-kernel@vger.kernel.org
Cc: Nuno Sa <nuno.sa@analog.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, Markus Burri <markus.burri@bbv.ch>
Subject: Re: [PATCH v3] iio: backend: fix out-of-bound write
Date: Tue, 06 May 2025 07:48:20 +0100 [thread overview]
Message-ID: <bf75a685e8e94a90a84123122994592a505b8d02.camel@gmail.com> (raw)
In-Reply-To: <20250505203830.5117-1-markus.burri@mt.com>
On Mon, 2025-05-05 at 22:38 +0200, Markus Burri wrote:
> The buffer is set to 80 character. If a caller write more characters,
> count is truncated to the max available space in "simple_write_to_buffer".
> But afterwards a string terminator is written to the buffer at offset count
> without boundary check. The zero termination is written OUT-OF-BOUND.
>
> Add a check that the given buffer is smaller then the buffer to prevent.
>
> Fixes: 035b4989211d ("iio: backend: make sure to NULL terminate stack buffer")
> Signed-off-by: Markus Burri <markus.burri@mt.com>
> ---
LGTM
Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> drivers/iio/industrialio-backend.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-
> backend.c
> index a43c8d1bb3d0..4a364e038449 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -155,11 +155,14 @@ static ssize_t iio_backend_debugfs_write_reg(struct file
> *file,
> ssize_t rc;
> int ret;
>
> + if (count >= sizeof(buf) - 1)
> + return -ENOSPC;
> +
> rc = simple_write_to_buffer(buf, sizeof(buf) - 1, ppos, userbuf, count);
> if (rc < 0)
> return rc;
>
> - buf[count] = '\0';
> + buf[rc] = '\0';
you could have mentioned this change in the commit message...
>
> ret = sscanf(buf, "%i %i", &back->cached_reg_addr, &val);
>
>
> base-commit: b4432656b36e5cc1d50a1f2dc15357543add530e
next prev parent reply other threads:[~2025-05-06 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 20:38 Markus Burri
2025-05-06 6:48 ` Nuno Sá [this message]
2025-05-06 17:00 ` David Lechner
2025-05-07 6:23 ` Nuno Sá
2025-05-07 7:21 ` EXTERNAL - " Markus Burri
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=bf75a685e8e94a90a84123122994592a505b8d02.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.burri@bbv.ch \
--cc=markus.burri@mt.com \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.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®