linux-kernel - Re: [PATCH v2] spi: fsl-cpm: Check length parity before switching to 16 bit mode

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: <176580718122.161463.3716236495970643565.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:41 +0900
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 Christophe Leroy <chleroy@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 "florent . trinh-thai @ cs-soprasteria . com" <florent.trinh-thai@...soprasteria.com>, 
 stable@...r.kernel.org, Alexander Sverdlin <alexander.sverdlin@...il.com>
Subject: Re: [PATCH v2] spi: fsl-cpm: Check length parity before switching
 to 16 bit mode

On Thu, 20 Nov 2025 09:34:49 +0100, Christophe Leroy wrote:
> Commit fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers
> with even size") failed to make sure that the size is really even
> before switching to 16 bit mode. Until recently the problem went
> unnoticed because kernfs uses a pre-allocated bounce buffer of size
> PAGE_SIZE for reading EEPROM.
> 
> But commit 8ad6249c51d0 ("eeprom: at25: convert to spi-mem API")
> introduced an additional dynamically allocated bounce buffer whose size
> is exactly the size of the transfer, leading to a buffer overrun in
> the fsl-cpm driver when that size is odd.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: fsl-cpm: Check length parity before switching to 16 bit mode
      commit: 1417927df8049a0194933861e9b098669a95c762

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark