From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64133: ALSA: asihpi: Fix potential OOB array access at reading cache
Date: Sun, 19 Jul 2026 17:39:55 +0200 [thread overview]
Message-ID: <2026071927-CVE-2026-64133-e669@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: asihpi: Fix potential OOB array access at reading cache
find_control() to retrieve a cached info accesses the array with the
given index blindly, which may lead to an OOB array access.
Add a sanity check for avoiding it.
The Linux kernel CVE team has assigned CVE-2026-64133 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.258 with commit e060e21fe9cca1e5eafd8a1c597026577771e8d9
Fixed in 5.15.209 with commit 34d0d492a2812b9289af14bca3573a89275965b2
Fixed in 6.1.175 with commit ffa29cea7bf9a4ef2ea8084967f142e0301ac670
Fixed in 6.6.142 with commit 7b6f8c8eb93f02a74b1de8e521c0952af10d1f43
Fixed in 6.12.92 with commit 8778386e4387b28f2bf8425d7ffc667c6294457f
Fixed in 6.18.34 with commit 61c5017c64e2ac9e10b70b14b17a079dbc0a805f
Fixed in 7.0.11 with commit 7d107239935793995bdc6cf29bb99e180bde4c28
Fixed in 7.1 with commit 7b7d6572145c1dab2dd9bfb550b188e5f0ff3c3f
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-64133
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/pci/asihpi/hpicmn.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/e060e21fe9cca1e5eafd8a1c597026577771e8d9
https://git.kernel.org/stable/c/34d0d492a2812b9289af14bca3573a89275965b2
https://git.kernel.org/stable/c/ffa29cea7bf9a4ef2ea8084967f142e0301ac670
https://git.kernel.org/stable/c/7b6f8c8eb93f02a74b1de8e521c0952af10d1f43
https://git.kernel.org/stable/c/8778386e4387b28f2bf8425d7ffc667c6294457f
https://git.kernel.org/stable/c/61c5017c64e2ac9e10b70b14b17a079dbc0a805f
https://git.kernel.org/stable/c/7d107239935793995bdc6cf29bb99e180bde4c28
https://git.kernel.org/stable/c/7b7d6572145c1dab2dd9bfb550b188e5f0ff3c3f
reply other threads:[~2026-07-19 15:45 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=2026071927-CVE-2026-64133-e669@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.