linux-kernel - Re: [PATCH next] ASoC: sma1307: Fix error handling in sma1307_setting

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: <174300492606.114957.8504606772761953074.b4-ty@kernel.org>
Date: Wed, 26 Mar 2025 16:02:06 +0000
From: Mark Brown <broonie@...nel.org>
To: Chenyuan Yang <chenyuan0y@...il.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Kiseok Jo <kiseok.jo@...ndevice.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] ASoC: sma1307: Fix error handling in
 sma1307_setting_loaded()

On Fri, 21 Mar 2025 17:35:25 +0300, Dan Carpenter wrote:
> There are a couple bugs in this code:
> 
> 1) The cleanup code calls kfree(sma1307->set.header) and
>    kfree(sma1307->set.def) but those functions were allocated using
>    devm_kzalloc().  It results in a double free.  Delete all these
>    kfree() calls.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: sma1307: Fix error handling in sma1307_setting_loaded()
      commit: 012a6efcc805308b1d90a1056ba963eb08858645

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