linux-kernel - Re: [PATCH v3] spi: cadence: Fix out-of-bounds array access in cdns_mrvl_xspi_setup

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: <174344473636.164633.1724471826311364083.b4-ty@kernel.org>
Date: Mon, 31 Mar 2025 19:12:16 +0100
From: Mark Brown <broonie@...nel.org>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, 
 Witold Sadowski <wsadowski@...vell.com>, Ingo Molnar <mingo@...nel.org>, 
 Peter Zijlstra <peterz@...radead.org>, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v3] spi: cadence: Fix out-of-bounds array access in
 cdns_mrvl_xspi_setup_clock()

On Mon, 31 Mar 2025 08:33:32 -0700, Josh Poimboeuf wrote:
> If requested_clk > 128, cdns_mrvl_xspi_setup_clock() iterates over the
> entire cdns_mrvl_xspi_clk_div_list array without breaking out early,
> causing 'i' to go beyond the array bounds.
> 
> Fix that by stopping the loop when it gets to the last entry, clamping
> the clock to the minimum 6.25 MHz.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: cadence: Fix out-of-bounds array access in cdns_mrvl_xspi_setup_clock()
      commit: 7ba0847fa1c22e7801cebfe5f7b75aee4fae317e

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