linux-kernel - Re: [PATCH] ASoC: SOF: ipc3-dtrace: fix potential integer overflow in allocation

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: <175828644460.102649.6097725617056769364.b4-ty@kernel.org>
Date: Fri, 19 Sep 2025 13:54:04 +0100
From: Mark Brown <broonie@...nel.org>
To: peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com, 
 ranjani.sridharan@...ux.intel.com, linux-sound@...r.kernel.org, 
 sound-open-firmware@...a-project.org, 
 Samasth Norway Ananda <samasth.norway.ananda@...cle.com>
Cc: linux-kernel@...r.kernel.org, lgirdwood@...il.com, 
 daniel.baluta@....com
Subject: Re: [PATCH] ASoC: SOF: ipc3-dtrace: fix potential integer overflow
 in allocation

On Tue, 09 Sep 2025 15:51:11 -0700, Samasth Norway Ananda wrote:
> Fix a potential integer overflow vulnerability in trace_filter_parse()
> where the allocation size calculation could overflow.
> 
> The issue occurs when:
> 1. capacity is calculated by adding TRACE_FILTER_ELEMENTS_PER_ENTRY in a
>    loop for each entry found in the input string.
> 2. capacity * sizeof(**out) multiplication could overflow if many
>    entries are present in the input.
> 3. This results in a smaller allocation than expected, leading to
>    potential buffer overflow.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: ipc3-dtrace: fix potential integer overflow in allocation
      commit: ce2335cd14b6585d57dc05a4375a506079adba81

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