linux-kernel - Re: [PATCH] mtd: fix possible integer overflow in erase

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175035329221.438255.2990702769206013816.b4-ty@bootlin.com>
Date: Thu, 19 Jun 2025 19:14:52 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Ivan Stepchenko <sid@....spb.ru>
Cc: Richard Weinberger <richard@....at>, 
 Vignesh Raghavendra <vigneshr@...com>, linux-mtd@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: [PATCH] mtd: fix possible integer overflow in erase_xfer()

On Thu, 19 Jun 2025 17:53:13 +0300, Ivan Stepchenko wrote:
> The expression '1 << EraseUnitSize' is evaluated in int, which causes
> a negative result when shifting by 31 - the upper bound of the valid
> range [10, 31], enforced by scan_header(). This leads to incorrect
> extension when storing the result in 'erase->len' (uint64_t), producing
> a large unexpected value.
> 
> Found by Linux Verification Center (linuxtesting.org) with Svace.
> 
> [...]

Applied to mtd/next, thanks!

[1/1] mtd: fix possible integer overflow in erase_xfer()
      commit: 9358bdb9f9f54d94ceafc650deffefd737d19fdd

Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).

Kind regards,
Miquèl