public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Anton Moryakov <ant.v.moryakov@gmail.com>,
	<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH mtd-utils] nand-utils: Fix integer overflow in nandflipbits.c
Date: Wed, 18 Dec 2024 10:50:40 +0800	[thread overview]
Message-ID: <d9ca5f92-cf0c-ff53-7609-7ba10886b6ef@huawei.com> (raw)
In-Reply-To: <20241217163653.298586-1-ant.v.moryakov@gmail.com>

在 2024/12/18 0:36, Anton Moryakov 写道:
> Report of the static analyzer:
> The value of an arithmetic expression 'page * (mtd.min_io_size + mtd.oob_size)' is a subject to overflow because its operands are not cast to a larger data type before performing arithmetic
> 
> Corrections explained:
> Casting bit_to_flip->block to unsigned long long expands the range of values ​​and allows the result of the multiplication to be calculated in a wider data type.
> The arithmetic is performed in a safe range, preventing overflow.
> Sum + blkoffs is now also safe, since the result of the expression is already calculated in unsigned long long.
> 
> Triggers found by static analyzer Svace.
> 
> Signed-off-by: Anton Moryakov <ant.v.moryakov@gmail.com>
> 
> ---
>   nand-utils/nandflipbits.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/nand-utils/nandflipbits.c b/nand-utils/nandflipbits.c
> index ef663c6..c4642fe 100644
> --- a/nand-utils/nandflipbits.c
> +++ b/nand-utils/nandflipbits.c
> @@ -213,7 +213,7 @@ int main(int argc, char **argv)
>   		bits_to_flip[i].block = bits_to_flip[i].offset / blklen;
>   		bits_to_flip[i].offset %= blklen;
>   		page = bits_to_flip[i].offset / pagelen;
> -		bits_to_flip[i].offset = (page *
> +		bits_to_flip[i].offset = ((unsigned long long)page *
>   					  (mtd.min_io_size + mtd.oob_size)) +
>   					 (bits_to_flip[i].offset % pagelen);

I think the 'bits_to_flip[i].offset' is limited smaller than 
'mtd.eb_size' by the code:
  bits_to_flip[i].offset %= blklen;
  page = bits_to_flip[i].offset / pagelen;
So, I don't think an overflow could happen here.
>   	}
> 


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2024-12-18  2:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 16:36 [PATCH mtd-utils] nand-utils: Fix integer overflow in nandflipbits.c Anton Moryakov
2024-12-18  2:50 ` Zhihao Cheng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-14 12:18 Anton Moryakov
2024-12-16  1:08 ` Zhihao Cheng
2024-12-13 13:19 Anton Moryakov
2024-12-14  2:59 ` Zhihao Cheng
2024-12-12 18:39 Anton Moryakov
2024-12-13  2:37 ` Zhihao Cheng

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=d9ca5f92-cf0c-ff53-7609-7ba10886b6ef@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=ant.v.moryakov@gmail.com \
    --cc=linux-mtd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox