[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171985009864.89113.4517197771955831374.b4-ty@kernel.org>
Date: Mon, 01 Jul 2024 17:08:18 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com,
alsa-devel@...a-project.org, linux-sound@...r.kernel.org
Subject: Re: [PATCH 0/4] firmware: cs_dsp: Add check to prevent overrunning
the firmware file
On Thu, 27 Jun 2024 15:14:28 +0100, Richard Fitzgerald wrote:
> This series fixes various missing length checks when processing
> variable-length data from the firmware file. These could have
> caused overrunning the end of firmware file buffer, or wild
> pointer accesses.
>
> Richard Fitzgerald (4):
> firmware: cs_dsp: Fix overflow checking of wmfw header
> firmware: cs_dsp: Return error if block header overflows file
> firmware: cs_dsp: Validate payload length before processing block
> firmware: cs_dsp: Prevent buffer overrun when processing V2 alg
> headers
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] firmware: cs_dsp: Fix overflow checking of wmfw header
commit: 3019b86bce16fbb5bc1964f3544d0ce7d0137278
[2/4] firmware: cs_dsp: Return error if block header overflows file
commit: 959fe01e85b7241e3ec305d657febbe82da16a02
[3/4] firmware: cs_dsp: Validate payload length before processing block
commit: 6598afa9320b6ab13041616950ca5f8f938c0cf1
[4/4] firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers
commit: 2163aff6bebbb752edf73f79700f5e2095f3559e
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
Powered by blists - more mailing lists