From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
<alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>
Subject: [PATCH 0/4] firmware: cs_dsp: Add check to prevent overrunning the firmware file
Date: Thu, 27 Jun 2024 15:14:28 +0100 [thread overview]
Message-ID: <20240627141432.93056-1-rf@opensource.cirrus.com> (raw)
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
drivers/firmware/cirrus/cs_dsp.c | 223 ++++++++++++++++++++++---------
1 file changed, 160 insertions(+), 63 deletions(-)
--
2.39.2
next reply other threads:[~2024-06-27 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:14 Richard Fitzgerald [this message]
2024-06-27 14:14 ` [PATCH 1/4] firmware: cs_dsp: Fix overflow checking of wmfw header Richard Fitzgerald
2024-06-27 14:14 ` [PATCH 2/4] firmware: cs_dsp: Return error if block header overflows file Richard Fitzgerald
2024-06-27 14:14 ` [PATCH 3/4] firmware: cs_dsp: Validate payload length before processing block Richard Fitzgerald
2024-06-27 14:14 ` [PATCH 4/4] firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers Richard Fitzgerald
2024-07-01 16:08 ` [PATCH 0/4] firmware: cs_dsp: Add check to prevent overrunning the firmware file Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240627141432.93056-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox