linux-kernel - Re: [PATCH] ASoC: rsnd: fix OF node reference leak in rsnd_ssiu

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: <176303826968.17893.10351782135097925928.b4-ty@kernel.org>
Date: Thu, 13 Nov 2025 12:51:09 +0000
From: Mark Brown <broonie@...nel.org>
To: kuninori.morimoto.gx@...esas.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, geert+renesas@...der.be, magnus.damm@...il.com, 
 Haotian Zhang <vulab@...as.ac.cn>
Cc: linux-sound@...r.kernel.org, linux-renesas-soc@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: rsnd: fix OF node reference leak in
 rsnd_ssiu_probe()

On Wed, 12 Nov 2025 14:57:09 +0800, Haotian Zhang wrote:
> rsnd_ssiu_probe() leaks an OF node reference obtained by
> rsnd_ssiu_of_node(). The node reference is acquired but
> never released across all return paths.
> 
> Fix it by declaring the device node with the __free(device_node)
> cleanup construct to ensure automatic release when the variable goes
> out of scope.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: rsnd: fix OF node reference leak in rsnd_ssiu_probe()
      commit: 360b3730f8eab6c4467c6cca4cb0e30902174a63

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