Re: [PATCH 0/4] ASoC: Validate written enum values in custom controls

From: Mark Brown

Date: Fri Jun 12 2026 - 18:20:05 EST


On Tue, 09 Jun 2026 21:43:12 +0900, HyeongJun An wrote:
> ASoC: Validate written enum values in custom controls
>
> Some custom ASoC kcontrol put() handlers use the written enum value
> (ucontrol->value.enumerated.item[0]) to index a table or compute a bit
> shift before validating that the value is within the control's enum range.
> An out-of-range value written from userspace is therefore consumed before
> it is rejected.
>
> [...]

Applied to

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

Thanks!

[1/4] ASoC: codecs: hdac_hdmi: Validate written enum value
https://git.kernel.org/broonie/sound/c/0b08baeccdcf
[2/4] ASoC: meson: aiu: Validate written enum values
https://git.kernel.org/broonie/sound/c/d65adf854772
[3/4] ASoC: fsl: fsl_audmix: Validate written enum values
https://git.kernel.org/broonie/sound/c/3cd17e4e2871
[4/4] ASoC: tegra: tegra210_ahub: Validate written enum value
https://git.kernel.org/broonie/sound/c/1d8aabb413b5

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