linux-kernel - Re: [PATCH 1/1] ASoC: simple-card-utils: Fix pointer check in graph_util_parse_link

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: <174607819946.4025361.17609297159298131450.b4-ty@kernel.org>
Date: Thu, 01 May 2025 14:43:19 +0900
From: Mark Brown <broonie@...nel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Alexander Stein <alexander.stein@...tq-group.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ASoC: simple-card-utils: Fix pointer check in
 graph_util_parse_link_direction

On Tue, 29 Apr 2025 11:49:10 +0200, Alexander Stein wrote:
> Actually check if the passed pointers are valid, before writing to them.
> This also fixes a USBAN warning:
> UBSAN: invalid-load in ../sound/soc/fsl/imx-card.c:687:25
> load of value 255 is not a valid value for type '_Bool'
> 
> This is because playback_only is uninitialized and is not written to, as
> the playback-only property is absent.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: simple-card-utils: Fix pointer check in graph_util_parse_link_direction
      commit: 3cc393d2232ec770b5f79bf0673d67702a3536c3

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