From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-42237: firmware: cs_dsp: Validate payload length before processing block
Date: Wed, 7 Aug 2024 17:14:43 +0200 [thread overview]
Message-ID: <2024080740-CVE-2024-42237-eba4@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
firmware: cs_dsp: Validate payload length before processing block
Move the payload length check in cs_dsp_load() and cs_dsp_coeff_load()
to be done before the block is processed.
The check that the length of a block payload does not exceed the number
of remaining bytes in the firwmware file buffer was being done near the
end of the loop iteration. However, some code before that check used the
length field without validating it.
The Linux kernel CVE team has assigned CVE-2024-42237 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit f6bc909e7673 and fixed in 6.1.100 with commit 259955eca9b7
Issue introduced in 5.16 with commit f6bc909e7673 and fixed in 6.6.41 with commit 3a9cd924aec1
Issue introduced in 5.16 with commit f6bc909e7673 and fixed in 6.9.10 with commit 71d9e313d8f7
Issue introduced in 5.16 with commit f6bc909e7673 and fixed in 6.10 with commit 6598afa9320b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-42237
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/firmware/cirrus/cs_dsp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/259955eca9b7acf1299b1ac077d8cfbe12df35d8
https://git.kernel.org/stable/c/3a9cd924aec1288d675df721f244da4dd7e16cff
https://git.kernel.org/stable/c/71d9e313d8f7e18c543a9c80506fe6b1eb1fe0c8
https://git.kernel.org/stable/c/6598afa9320b6ab13041616950ca5f8f938c0cf1
reply other threads:[~2024-08-07 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2024080740-CVE-2024-42237-eba4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.