linux-kernel - Re: [PATCH] ASoC: amd/sdw_utils: avoid NULL deref when 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 for Android: free password hash cracker in your pocket

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

Message-Id: <176061852278.55339.14706460406632258362.b4-ty@kernel.org>
Date: Thu, 16 Oct 2025 13:42:02 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 Li Qiang <liqiang01@...inos.cn>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd/sdw_utils: avoid NULL deref when
 devm_kasprintf() fails

On Wed, 15 Oct 2025 15:55:30 +0800, Li Qiang wrote:
> devm_kasprintf() may return NULL on memory allocation failure,
> but the debug message prints cpus->dai_name before checking it.
> Move the dev_dbg() call after the NULL check to prevent potential
> NULL pointer dereference.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd/sdw_utils: avoid NULL deref when devm_kasprintf() fails
      commit: 5726b68473f7153a7f6294185e5998b7e2a230a2

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