linux-kernel - Re: [PATCH] ASoC: wm_adsp: Use vmemdup

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: <174434800810.1298095.3518873899579787248.b4-ty@kernel.org>
Date: Fri, 11 Apr 2025 06:06:48 +0100
From: Mark Brown <broonie@...nel.org>
To: 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: wm_adsp: Use vmemdup_user() instead of
 open-coding

On Thu, 10 Apr 2025 11:18:12 +0100, Richard Fitzgerald wrote:
> Use vmemdup_user() to get a copy of the user buffer in wm_coeff_tlv_put().
> 
> Apart from simplifying the code and avoiding open-coding, it means we
> also automatically benefit from any security enhancements in the code
> behind vmemdup_user().
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm_adsp: Use vmemdup_user() instead of open-coding
      commit: b5d057a86e2086af0b1e6d0ca8b306be1c73a627

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