From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80972: ALSA: aloop: Check card index validity at probe
Date: Fri, 11 Sep 2026 21:41:18 +0200 [thread overview]
Message-ID: <2026091144-CVE-2026-80972-9ab1@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: aloop: Check card index validity at probe
aloop driver blindly trusts that the given devptr->id value is within
the proper card index range at probe. It's OK for the devices the
driver itself creates at the module probe time, but if the device is
bound manually via sysfs interface, this could be -1 as "none", and
this leads to OOB access for index[] and other parameters.
Add a sanity check for the card index and warn/correct it if it's a
value out of the range.
The Linux kernel CVE team has assigned CVE-2026-80972 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.109 with commit c589aeaadfde1cfedb5c6f0a3c782807282126d9
Fixed in 6.18.50 with commit 7b3f9855849363e402bf2141df2b428581cbf31b
Fixed in 7.2.4 with commit efbc2e9e43a1b5c6d75ae47439c06896bb142ae6
Fixed in 7.3-rc1 with commit 819b106a9fd2ef3fd8abf898b9a8e4524eca8f48
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-80972
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/drivers/aloop.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/c589aeaadfde1cfedb5c6f0a3c782807282126d9
https://git.kernel.org/stable/c/7b3f9855849363e402bf2141df2b428581cbf31b
https://git.kernel.org/stable/c/efbc2e9e43a1b5c6d75ae47439c06896bb142ae6
https://git.kernel.org/stable/c/819b106a9fd2ef3fd8abf898b9a8e4524eca8f48
reply other threads:[~2026-09-11 19:47 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=2026091144-CVE-2026-80972-9ab1@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.