linux-kernel - Re: [PATCH] firmware: cs_dsp: Don't allow writes to read-only controls

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: <171994340097.996226.8732396451392780066.b4-ty@kernel.org>
Date: Tue, 02 Jul 2024 19:03:20 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Don't allow writes to read-only
 controls

On Tue, 02 Jul 2024 12:08:09 +0100, Richard Fitzgerald wrote:
> Add a check to cs_dsp_coeff_write_ctrl() to abort if the control
> is not writeable.
> 
> The cs_dsp code originated as an ASoC driver (wm_adsp) where all
> controls were exported as ALSA controls. It relied on ALSA to
> enforce the read-only permission. Now that the code has been
> separated from ALSA/ASoC it must perform its own permission check.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Don't allow writes to read-only controls
      commit: 62412a9357b16a4e39dc582deb2e2a682b92524c

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