linux-kernel - Re: [PATCH] regulator: ti-abb: Fix array out of bound read access on the first transition

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: <160573318504.46660.3881026259686236737.b4-ty@kernel.org>
Date:   Wed, 18 Nov 2020 20:59:45 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Nishanth Menon <nm@...com>, Liam Girdwood <lgirdwood@...il.com>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        linux-pm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        lkft-triage@...ts.linaro.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] regulator: ti-abb: Fix array out of bound read access on the first transition

On Wed, 18 Nov 2020 08:50:09 -0600, Nishanth Menon wrote:
> At the start of driver initialization, we do not know what bias
> setting the bootloader has configured the system for and we only know
> for certain the very first time we do a transition.
> 
> However, since the initial value of the comparison index is -EINVAL,
> this negative value results in an array out of bound access on the
> very first transition.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: ti-abb: Fix array out of bound read access on the first transition
      commit: 2ba546ebe0ce2af47833d8912ced9b4a579f13cb

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