linux-kernel - Re: [PATCH v2] regulator: tps65219: Fix devm

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: <175128363906.28827.3502546879680346196.b4-ty@kernel.org>
Date: Mon, 30 Jun 2025 12:40:39 +0100
From: Mark Brown <broonie@...nel.org>
To: aaro.koskinen@....fi, andreas@...nade.info, khilman@...libre.com, 
 rogerq@...nel.org, tony@...mide.com, lee@...nel.org, d-gole@...com, 
 robertcnelson@...il.com, jkridner@...il.com, linux-omap@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Shree Ramamoorthy <s-ramamoorthy@...com>
Cc: m-leonard@...com, praneeth@...com, afd@...com
Subject: Re: [PATCH v2] regulator: tps65219: Fix devm_kmalloc size
 allocation

On Fri, 20 Jun 2025 10:45:41 -0500, Shree Ramamoorthy wrote:
> In probe(), two arrays of structs are allocated with the devm_kmalloc()
> function, but the memory size of the allocations were given as the arrays'
> length (pmic->common_irq_size for the first call and pmic->dev_irq_size for
> the second devm_kmalloc call). The memory size should have been the total
> memory needed.
> 
> This led to a heap overflow when the struct array was used. The issue was
> first discovered with the PocketBeagle2 and BeaglePlay. The common and
> device-specific structs are now allocated one at a time within the loop.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: tps65219: Fix devm_kmalloc size allocation
      commit: eeca209124bb694650026216d3e59cae02d91686

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