linux-kernel - Re: [PATCH] regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods

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: <175156004152.634143.17330857635962840361.b4-ty@kernel.org>
Date: Thu, 03 Jul 2025 17:27:21 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, Manivannan Sadhasivam <mani@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] regulator: gpio: Fix the out-of-bounds access to
 drvdata::gpiods

On Thu, 03 Jul 2025 16:05:49 +0530, Manivannan Sadhasivam wrote:
> drvdata::gpiods is supposed to hold an array of 'gpio_desc' pointers. But
> the memory is allocated for only one pointer. This will lead to
> out-of-bounds access later in the code if 'config::ngpios' is > 1. So
> fix the code to allocate enough memory to hold 'config::ngpios' of GPIO
> descriptors.
> 
> While at it, also move the check for memory allocation failure to be below
> the allocation to make it more readable.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods
      commit: c9764fd88bc744592b0604ccb6b6fc1a5f76b4e3

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