linux-kernel - Re: [PATCH] ASoC: davinci-evm: Fix reference leak in davinci_evm

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176797257322.63356.4907810860589912979.b4-ty@kernel.org>
Date: Fri, 09 Jan 2026 15:29:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Kery Qi <qikeyu2017@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: davinci-evm: Fix reference leak in
 davinci_evm_probe

On Wed, 07 Jan 2026 23:48:37 +0800, Kery Qi wrote:
> The davinci_evm_probe() function calls of_parse_phandle() to acquire
> device nodes for "ti,audio-codec" and "ti,mcasp-controller". These
> functions return device nodes with incremented reference counts.
> 
> However, in several error paths (e.g., when the second of_parse_phandle(),
> snd_soc_of_parse_card_name(), or devm_snd_soc_register_card() fails),
> the function returns directly without releasing the acquired nodes,
> leading to reference leaks.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: davinci-evm: Fix reference leak in davinci_evm_probe
      commit: 5b577d214fcc109707bcb77b4ae72a31cfd86798

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