From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26927: ASoC: SOF: Add some bounds checking to firmware data
Date: Sun, 28 Apr 2024 13:35:43 +0200 [thread overview]
Message-ID: <2024042844-CVE-2024-26927-3374@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: Add some bounds checking to firmware data
Smatch complains about "head->full_size - head->header_size" can
underflow. To some extent, we're always going to have to trust the
firmware a bit. However, it's easy enough to add a check for negatives,
and let's add a upper bounds check as well.
The Linux kernel CVE team has assigned CVE-2024-26927 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit d2458baa799f and fixed in 6.1.83 with commit d133d67e7e72
Issue introduced in 5.19 with commit d2458baa799f and fixed in 6.6.23 with commit ced7df8b3c5c
Issue introduced in 5.19 with commit d2458baa799f and fixed in 6.7.11 with commit 044e22066715
Issue introduced in 5.19 with commit d2458baa799f and fixed in 6.8.2 with commit 9eeb8e1231f6
Issue introduced in 5.19 with commit d2458baa799f and fixed in 6.9-rc1 with commit 98f681b0f84c
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-26927
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:
sound/soc/sof/ipc3-loader.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/d133d67e7e724102d1e53009c4f88afaaf3e167c
https://git.kernel.org/stable/c/ced7df8b3c5c4751244cad79011e86cf1f809153
https://git.kernel.org/stable/c/044e220667157fb9d59320341badec59cf45ba48
https://git.kernel.org/stable/c/9eeb8e1231f6450c574c1db979122e171a1813ab
https://git.kernel.org/stable/c/98f681b0f84cfc3a1d83287b77697679e0398306
next reply other threads:[~2024-04-28 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 11:35 Greg Kroah-Hartman [this message]
2024-04-28 11:35 ` CVE-2024-26928: smb: client: fix potential UAF in cifs_debug_files_proc_show() Greg Kroah-Hartman
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=2024042844-CVE-2024-26927-3374@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.