From: William Zhang <william.zhang@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>,
u-boot@lists.denx.de,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Anand Gore <anand.gore@broadcom.com>,
Kursad Oney <kursad.oney@broadcom.com>,
Philippe Reynes <philippe.reynes@softathome.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: RE: [PATCH v2 3/7] mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write
Date: Mon, 16 Sep 2024 17:22:02 -0700 [thread overview]
Message-ID: <f75b41253f3f3677d11827d8b6c306d3@mail.gmail.com> (raw)
In-Reply-To: <20240916-brcmnand-fixes-v2-3-08632f64c8ec@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
> -----Original Message-----
> From: Linus Walleij <linus.walleij@linaro.org>
> Sent: Monday, September 16, 2024 2:59 AM
> To: u-boot@lists.denx.de; Dario Binacchi
> <dario.binacchi@amarulasolutions.com>; Michael Trimarchi
> <michael@amarulasolutions.com>; Anand Gore
> <anand.gore@broadcom.com>; William Zhang
> <william.zhang@broadcom.com>; Kursad Oney
> <kursad.oney@broadcom.com>; Philippe Reynes
> <philippe.reynes@softathome.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>; Florian Fainelli
> <florian.fainelli@broadcom.com>; Miquel Raynal
> <miquel.raynal@bootlin.com>
> Subject: [PATCH v2 3/7] mtd: rawnand: brcmnand: Fix potential out-of-
> bounds access in oob write
>
> From: William Zhang <william.zhang@broadcom.com>
>
> Backport of upstream Linux
> commit 5d53244186c9ac58cb88d76a0958ca55b83a15cd
> "mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write"
>
> When the oob buffer length is not in multiple of words, the oob write
> function does out-of-bounds read on the oob source buffer at the last
> iteration. Fix that by always checking length limit on the oob buffer
> read and fill with 0xff when reaching the end of the buffer to the oob
> registers.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Link: https://lore.kernel.org/linux-mtd/20230706182909.79151-5-
> william.zhang@broadcom.com
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/mtd/nand/raw/brcmnand/brcmnand.c | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> index 46a4107a83a9..60d34bd21f53 100644
> --- a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> @@ -1334,19 +1334,33 @@ static int write_oob_to_regs(struct
> brcmnand_controller *ctrl, int i,
> const u8 *oob, int sas, int sector_1k)
> {
> int tbytes = sas << sector_1k;
> - int j;
> + int j, k = 0;
> + u32 last = 0xffffffff;
> + u8 *plast = (u8 *)&last;
>
> /* Adjust OOB values for 1K sector size */
> if (sector_1k && (i & 0x01))
> tbytes = max(0, tbytes - (int)ctrl->max_oob);
> tbytes = min_t(int, tbytes, ctrl->max_oob);
>
> - for (j = 0; j < tbytes; j += 4)
> + /*
> + * tbytes may not be multiple of words. Make sure we don't read
> out of
> + * the boundary and stop at last word.
> + */
> + for (j = 0; (j + 3) < tbytes; j += 4)
> oob_reg_write(ctrl, j,
> (oob[j + 0] << 24) |
> (oob[j + 1] << 16) |
> (oob[j + 2] << 8) |
> (oob[j + 3] << 0));
> +
> + /* handle the remaing bytes */
> + while (j < tbytes)
> + plast[k++] = oob[j++];
> +
> + if (tbytes & 0x3)
> + oob_reg_write(ctrl, (tbytes & ~0x3), (__force
> u32)cpu_to_be32(last));
> +
> return tbytes;
> }
>
>
> --
> 2.46.0
Reviewed-by: William Zhang <william.zhang@broadcom.com>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next prev parent reply other threads:[~2024-09-17 0:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 9:58 [PATCH v2 0/7] mtd: nand: brcmnand: Backported fixes from Linux Linus Walleij
2024-09-16 9:58 ` [PATCH v2 1/7] mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller Linus Walleij
2024-09-17 0:21 ` William Zhang
2024-09-29 17:19 ` Michael Nazzareno Trimarchi
2024-09-16 9:58 ` [PATCH v2 2/7] mtd: rawnand: brcmnand: Fix potential false time out warning Linus Walleij
2024-09-17 0:20 ` William Zhang
2024-09-29 17:20 ` Michael Nazzareno Trimarchi
2024-09-16 9:58 ` [PATCH v2 3/7] mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write Linus Walleij
2024-09-17 0:22 ` William Zhang [this message]
2024-09-16 9:58 ` [PATCH v2 4/7] mtd: rawnand: brcmnand: Fix mtd oobsize Linus Walleij
2024-09-17 0:22 ` William Zhang
2024-09-16 9:58 ` [PATCH v2 5/7] mtd: rawnand: brcmnand: Add read data bus interface Linus Walleij
2024-09-17 0:22 ` William Zhang
2024-09-16 9:58 ` [PATCH v2 6/7] mtd: rawnand: brcmnand: Support write protection setting from dts Linus Walleij
2024-09-17 0:26 ` William Zhang
2024-09-16 9:58 ` [PATCH v2 7/7] mtd: rawnand: brcmnand: Add support for getting ecc setting from strap Linus Walleij
2024-09-17 0:31 ` William Zhang
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=f75b41253f3f3677d11827d8b6c306d3@mail.gmail.com \
--to=william.zhang@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=florian.fainelli@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=michael@amarulasolutions.com \
--cc=miquel.raynal@bootlin.com \
--cc=philippe.reynes@softathome.com \
--cc=u-boot@lists.denx.de \
/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