From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74292: ASoC: tegra: tegra210_ahub: Validate written enum value
Date: Sat, 15 Aug 2026 15:10:19 +0900 [thread overview]
Message-ID: <2026081548-CVE-2026-74292-7676@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: tegra: tegra210_ahub: Validate written enum value
tegra_ahub_put_value_enum() reads e->values[item[0]] before
checking whether item[0] is within the enum item range. The existing
check therefore happens too late to prevent an out-of-range read of the
values array.
Move the check before the array access.
The Linux kernel CVE team has assigned CVE-2026-74292 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 5.10.261 with commit 4e45e4c2015519a39c40eb575c03b77807fb5080
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 5.15.212 with commit 964f8f9015fb117402d8d2186593397cd93388e9
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 6.1.178 with commit 2ec7d16fe21c68b0879873a2abf9aac854c96134
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 6.6.145 with commit 4bcb23635d5059ee71f3fb89719ea14aada6fd59
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 6.12.97 with commit f67d63628fe158b3a6e6b33a2b8c83ff118699d1
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 6.18.40 with commit e098c9c6477dfa3cb363282100108484ceba5cc5
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 7.1.5 with commit 226d93b65f4f99b35fb7a03bdb24acb577364ebc
Issue introduced in 5.9 with commit 16e1bcc2caf446fa3e1daa040b59fd6f6272a766 and fixed in 7.2-rc1 with commit 1d8aabb413b5638670dfd1162169edc0ba276a2e
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-74292
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/tegra/tegra210_ahub.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/4e45e4c2015519a39c40eb575c03b77807fb5080
https://git.kernel.org/stable/c/964f8f9015fb117402d8d2186593397cd93388e9
https://git.kernel.org/stable/c/2ec7d16fe21c68b0879873a2abf9aac854c96134
https://git.kernel.org/stable/c/4bcb23635d5059ee71f3fb89719ea14aada6fd59
https://git.kernel.org/stable/c/f67d63628fe158b3a6e6b33a2b8c83ff118699d1
https://git.kernel.org/stable/c/e098c9c6477dfa3cb363282100108484ceba5cc5
https://git.kernel.org/stable/c/226d93b65f4f99b35fb7a03bdb24acb577364ebc
https://git.kernel.org/stable/c/1d8aabb413b5638670dfd1162169edc0ba276a2e
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-74292-7676@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.