linux-kernel - Re: [PATCH] regulator: max20086: Fix refcount leak in max20086_parse_regulators

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: <174947643393.126945.18182713164781359832.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 14:40:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Cosmin Tanislav <demonsingur@...il.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, 
 kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] regulator: max20086: Fix refcount leak in
 max20086_parse_regulators_dt()

On Tue, 27 May 2025 08:44:14 +0300, Dan Carpenter wrote:
> There is a missing call to of_node_put() if devm_kcalloc() fails.
> Fix this by changing the code to use cleanup.h magic to drop the
> refcount.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: max20086: Fix refcount leak in max20086_parse_regulators_dt()
      commit: 06118ae36855b7d3d22688298e74a766ccf0cb7a

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