From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74332: ASoC: amd: acp-sdw-sof: Bound DAI link iteration
Date: Sat, 15 Aug 2026 15:10:59 +0900 [thread overview]
Message-ID: <2026081555-CVE-2026-74332-d98e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: amd: acp-sdw-sof: Bound DAI link iteration
create_sdw_dailinks() walks sof_dais until it finds an entry with
initialised cleared, but sof_dais is allocated with exactly num_ends
entries. If all entries are initialised, the loop reads past the end of
the array.
Pass the allocated entry count to create_sdw_dailinks() and stop before
reading past the array.
The Linux kernel CVE team has assigned CVE-2026-74332 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 6d8348ddc56ed43ba39d1e8adda13299201f32ed and fixed in 6.12.97 with commit 0a5ff4000dd7a390139dd7823fef1de4963e490a
Issue introduced in 6.12 with commit 6d8348ddc56ed43ba39d1e8adda13299201f32ed and fixed in 6.18.40 with commit 9e82497138abea7d5c6e65015663d907fbcbf6b4
Issue introduced in 6.12 with commit 6d8348ddc56ed43ba39d1e8adda13299201f32ed and fixed in 7.1.5 with commit 86a64c049873fe4d4a6a378e27a333ab5631c4b2
Issue introduced in 6.12 with commit 6d8348ddc56ed43ba39d1e8adda13299201f32ed and fixed in 7.2-rc1 with commit 4d992e63f52d58f52b724606c60ae7b37a1c582f
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-2026-74332
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/amd/acp/acp-sdw-sof-mach.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/0a5ff4000dd7a390139dd7823fef1de4963e490a
https://git.kernel.org/stable/c/9e82497138abea7d5c6e65015663d907fbcbf6b4
https://git.kernel.org/stable/c/86a64c049873fe4d4a6a378e27a333ab5631c4b2
https://git.kernel.org/stable/c/4d992e63f52d58f52b724606c60ae7b37a1c582f
reply other threads:[~2026-08-15 6:37 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=2026081555-CVE-2026-74332-d98e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.