From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74293: ASoC: fsl: fsl_audmix: Validate written enum values
Date: Sat, 15 Aug 2026 15:10:20 +0900 [thread overview]
Message-ID: <2026081548-CVE-2026-74293-aa3d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: fsl: fsl_audmix: Validate written enum values
fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src()
convert the user-provided enum item with snd_soc_enum_item_to_val()
before checking whether the item is within the enum's item count.
The generic snd_soc_put_enum_double() helper performs that
validation, but these callbacks use the converted value first: the
clock-source path tests it with BIT(), and the output-source path
indexes the prms transition table with it.
Reject out-of-range enum items before converting them.
The Linux kernel CVE team has assigned CVE-2026-74293 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 5.10.261 with commit 7513831b90a38d55fa089e3e1b49691e467afee6
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 5.15.212 with commit b4774a7da12b14fc37219ab4368d1907f9b5aca4
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 6.1.178 with commit 8fb4364eb494b926d009bfaf3c98f07c3aa5d9f3
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 6.6.145 with commit 0b10c6203e62d9e7337cc401568b201f9bac79ec
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 6.12.97 with commit b36d6d48faa6b1bb723b8f4e527c531a1a68520e
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 6.18.40 with commit 0f1510e84d7bfc3eb9538efa65c6ea0aadf1078c
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 7.1.5 with commit 5b7a23c1ed04e794ef3b31e452ef5c93e1e34b4a
Issue introduced in 5.2 with commit be1df61cf06efb355c90702e46b8d46f055acb4e and fixed in 7.2-rc1 with commit 3cd17e4e2871114d5579fa7bc8da66faf7fc1930
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-74293
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/fsl/fsl_audmix.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/7513831b90a38d55fa089e3e1b49691e467afee6
https://git.kernel.org/stable/c/b4774a7da12b14fc37219ab4368d1907f9b5aca4
https://git.kernel.org/stable/c/8fb4364eb494b926d009bfaf3c98f07c3aa5d9f3
https://git.kernel.org/stable/c/0b10c6203e62d9e7337cc401568b201f9bac79ec
https://git.kernel.org/stable/c/b36d6d48faa6b1bb723b8f4e527c531a1a68520e
https://git.kernel.org/stable/c/0f1510e84d7bfc3eb9538efa65c6ea0aadf1078c
https://git.kernel.org/stable/c/5b7a23c1ed04e794ef3b31e452ef5c93e1e34b4a
https://git.kernel.org/stable/c/3cd17e4e2871114d5579fa7bc8da66faf7fc1930
reply other threads:[~2026-08-15 6:34 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=2026081548-CVE-2026-74293-aa3d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).