From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] nvmem/mxs-ocotp: fix buffer overflow in read
Date: Wed, 27 Apr 2016 14:24:33 +0200 [thread overview]
Message-ID: <5720AF81.2080402@i2se.com> (raw)
In-Reply-To: <201ccd58-8735-02d8-b4e4-9d2eda828fd8@meduna.org>
Hi Stano,
[add Srinivas and Maxime to CC]
Am 27.04.2016 um 13:53 schrieb Stanislav Meduna:
> This patch fixes the issue where the mxs_ocotp_read is reading
> the ocotp in reg_size steps but decrements the remaining size
> by 1. The number of iterations is thus four times higher,
> overwriting the area behind the output buffer.
please add your Signed-off-by here.
>
> Fixes: c01e9a11ab6f ("nvmem: add driver for ocotp in i.MX23 and i.MX28")
I tested the patch successful with i.MX23 and i.MX28.
Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
@Srinivas: I think this patch should go to stable.
Regards
> ---
> drivers/nvmem/mxs-ocotp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvmem/mxs-ocotp.c b/drivers/nvmem/mxs-ocotp.c
> index 8ba19bb..2bb3c57 100644
> --- a/drivers/nvmem/mxs-ocotp.c
> +++ b/drivers/nvmem/mxs-ocotp.c
> @@ -94,7 +94,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
> if (ret)
> goto close_banks;
>
> - while (val_size) {
> + while (val_size >= reg_size) {
> if ((offset < OCOTP_DATA_OFFSET) || (offset % 16)) {
> /* fill up non-data register */
> *buf = 0;
> @@ -103,7 +103,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
> }
>
> buf++;
> - val_size--;
> + val_size -= reg_size;
> offset += reg_size;
> }
>
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Stanislav Meduna <stano@meduna.org>
Cc: linux-kernel@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH] nvmem/mxs-ocotp: fix buffer overflow in read
Date: Wed, 27 Apr 2016 14:24:33 +0200 [thread overview]
Message-ID: <5720AF81.2080402@i2se.com> (raw)
In-Reply-To: <201ccd58-8735-02d8-b4e4-9d2eda828fd8@meduna.org>
Hi Stano,
[add Srinivas and Maxime to CC]
Am 27.04.2016 um 13:53 schrieb Stanislav Meduna:
> This patch fixes the issue where the mxs_ocotp_read is reading
> the ocotp in reg_size steps but decrements the remaining size
> by 1. The number of iterations is thus four times higher,
> overwriting the area behind the output buffer.
please add your Signed-off-by here.
>
> Fixes: c01e9a11ab6f ("nvmem: add driver for ocotp in i.MX23 and i.MX28")
I tested the patch successful with i.MX23 and i.MX28.
Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
@Srinivas: I think this patch should go to stable.
Regards
> ---
> drivers/nvmem/mxs-ocotp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvmem/mxs-ocotp.c b/drivers/nvmem/mxs-ocotp.c
> index 8ba19bb..2bb3c57 100644
> --- a/drivers/nvmem/mxs-ocotp.c
> +++ b/drivers/nvmem/mxs-ocotp.c
> @@ -94,7 +94,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
> if (ret)
> goto close_banks;
>
> - while (val_size) {
> + while (val_size >= reg_size) {
> if ((offset < OCOTP_DATA_OFFSET) || (offset % 16)) {
> /* fill up non-data register */
> *buf = 0;
> @@ -103,7 +103,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
> }
>
> buf++;
> - val_size--;
> + val_size -= reg_size;
> offset += reg_size;
> }
>
next prev parent reply other threads:[~2016-04-27 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:53 [PATCH] nvmem/mxs-ocotp: fix buffer overflow in read Stanislav Meduna
2016-04-27 11:53 ` Stanislav Meduna
2016-04-27 12:24 ` Stefan Wahren [this message]
2016-04-27 12:24 ` Stefan Wahren
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=5720AF81.2080402@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.