public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: kernel-janitors@vger.kernel.org
Subject: re: mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver
Date: Tue, 26 Jun 2018 15:18:29 +0000	[thread overview]
Message-ID: <993e40ac-1f06-c2ee-e9fb-4523df368cb7@canonical.com> (raw)

Hi there,

Static analysis with CoverityScan reported a potential issue with the
following commit:

commit 0f7b126ca91101d02d525f7cc880e8c71202a2b7
Author: Stefan Agner <stefan@agner.ch>
Date:   Sun Jun 24 23:27:25 2018 +0200

    mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver


in function tegra_nand_cmd it looks like there maybe potential to pass a
negative value in size into memcpy():

        case NAND_OP_DATA_OUT_INSTR:

negative_return_fn: Function nand_subop_get_data_len(subop, op_id)
returns a negative number.

var_assign: Assigning: unsigned variable size = nand_subop_get_data_len.

                size = nand_subop_get_data_len(subop, op_id);
                offset = nand_subop_get_data_start_off(subop, op_id);

                cmd |= COMMAND_TRANS_SIZE(size) | COMMAND_PIO |
                        COMMAND_TX | COMMAND_A_VALID;

Argument cannot be negative (NEGATIVE_RETURNS)65. negative_returns: size
is passed to a parameter that cannot be negative.
                memcpy(&reg, instr->ctx.data.buf.out + offset, size);


I also think the same issue may be happening with the
NAND_OP_DATA_IN_INSTR case too.

Colin

             reply	other threads:[~2018-06-26 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 15:18 Colin Ian King [this message]
2018-06-27  6:52 ` mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver Miquel Raynal

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=993e40ac-1f06-c2ee-e9fb-4523df368cb7@canonical.com \
    --to=colin.king@canonical.com \
    --cc=kernel-janitors@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