linux-kernel - Re: [v2][PATCH] regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator

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: <166143296648.103302.14963549343050177347.b4-ty@kernel.org>
Date:   Thu, 25 Aug 2022 14:09:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, Xiaolei Wang <xiaolei.wang@...driver.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [v2][PATCH] regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe()

On Thu, 25 Aug 2022 19:19:22 +0800, Xiaolei Wang wrote:
> The pfuze_chip::regulator_descs is an array of size
> PFUZE100_MAX_REGULATOR, the pfuze_chip::pfuze_regulators
> is the pointer to the real regulators of a specific device.
> The number of real regulator is supposed to be less than
> the PFUZE100_MAX_REGULATOR, so we should use the size of
> 'regulator_num * sizeof(struct pfuze_regulator)' in memcpy().
> This fixes the out of bounds access bug reported by KASAN.
>   BUG: KASAN: global-out-of-bounds in pfuze100_regulator_probe+0x380/0x8b8
>   Read of size 3968 at addr c3390640 by task swapper/0/1
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe()
      commit: 78e1e867f44e6bdc72c0e6a2609a3407642fb30b

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