linux-kernel - Re: [PATCH] regmap: maple: Fix cache corruption in regcache_maple

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: <171163501205.33337.6238909725521756529.b4-ty@kernel.org>
Date: Thu, 28 Mar 2024 14:10:12 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] regmap: maple: Fix cache corruption in
 regcache_maple_drop()

On Wed, 27 Mar 2024 11:44:06 +0000, Richard Fitzgerald wrote:
> When keeping the upper end of a cache block entry, the entry[] array
> must be indexed by the offset from the base register of the block,
> i.e. max - mas.index.
> 
> The code was indexing entry[] by only the register address, leading
> to an out-of-bounds access that copied some part of the kernel
> memory over the cache contents.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: maple: Fix cache corruption in regcache_maple_drop()
      commit: 00bb549d7d63a21532e76e4a334d7807a54d9f31

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