linux-kernel - Re: [PATCH] ASoC: qcom: Fix sc7280 lpass potential buffer overflow

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: <174406973881.1344763.7683351579116465463.b4-ty@kernel.org>
Date: Tue, 08 Apr 2025 00:48:58 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Evgeny Pimenov <pimenoveu12@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Venkata Prasad Potturu <quic_potturu@...cinc.com>, 
 Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>, 
 linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, lvc-patches@...uxtesting.org, 
 Fedor Pchelkin <pchelkin@...ras.ru>, Mikhail Kobuk <m.kobuk@...ras.ru>, 
 Alexey Khoroshilov <khoroshilov@...ras.ru>, stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: qcom: Fix sc7280 lpass potential buffer overflow

On Tue, 01 Apr 2025 23:40:58 +0300, Evgeny Pimenov wrote:
> Case values introduced in commit
> 5f78e1fb7a3e ("ASoC: qcom: Add driver support for audioreach solution")
> cause out of bounds access in arrays of sc7280 driver data (e.g. in case
> of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).
> 
> Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
> q6dsp as sc7280 driver utilizes some of those values.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: Fix sc7280 lpass potential buffer overflow
      commit: a31a4934b31faea76e735bab17e63d02fcd8e029

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