linux-kernel - Re: [PATCH] ASoC: Intel: sof_sdw: Prevent jump to NULL add

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: <175831279352.217357.15267982435869404784.b4-ty@kernel.org>
Date: Fri, 19 Sep 2025 21:13:13 +0100
From: Mark Brown <broonie@...nel.org>
To: yung-chuan.liao@...ux.intel.com, peter.ujfalusi@...ux.intel.com, 
 kai.vehmanen@...ux.intel.com, Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: Intel: sof_sdw: Prevent jump to NULL add_sidecar
 callback

On Fri, 19 Sep 2025 15:02:35 +0100, Richard Fitzgerald wrote:
> In create_sdw_dailink() check that sof_end->codec_info->add_sidecar
> is not NULL before calling it.
> 
> The original code assumed that if include_sidecar is true, the codec
> on that link has an add_sidecar callback. But there could be other
> codecs on the same link that do not have an add_sidecar callback.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: sof_sdw: Prevent jump to NULL add_sidecar callback
      commit: 87cab86925b7fa4c1c977bc191ac549a3b23f0ea

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