From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43436: ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces
Date: Fri, 8 May 2026 16:22:45 +0200 [thread overview]
Message-ID: <2026050852-CVE-2026-43436-9469@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces
The Scarlett2 mixer quirk in USB-audio driver may hit a NULL
dereference when a malformed USB descriptor is passed, since it
assumes the presence of an endpoint in the parsed interface in
scarlett2_find_fc_interface(), as reported by fuzzer.
For avoiding the NULL dereference, just add the sanity check of
bNumEndpoints and skip the invalid interface.
The Linux kernel CVE team has assigned CVE-2026-43436 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.167 with commit b014cc945baba75816cda0cf8934be87c9ed4947
Fixed in 6.6.130 with commit c5c5a6c53cf3b658f1d4512dfa61f3cd25bc34ba
Fixed in 6.12.78 with commit b267255c15d2a5b90c4e926146aa155e5161e264
Fixed in 6.18.19 with commit 3d542cf3c4c854cdf5d58049771f68926b9eb2b9
Fixed in 6.19.9 with commit 3d4f23885e4b90347c9a1d779af6e79a99b5172a
Fixed in 7.0 with commit df1d8abf36ca3681c21a6809eaa9a1e01ef897a6
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-43436
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/usb/mixer_scarlett2.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/b014cc945baba75816cda0cf8934be87c9ed4947
https://git.kernel.org/stable/c/c5c5a6c53cf3b658f1d4512dfa61f3cd25bc34ba
https://git.kernel.org/stable/c/b267255c15d2a5b90c4e926146aa155e5161e264
https://git.kernel.org/stable/c/3d542cf3c4c854cdf5d58049771f68926b9eb2b9
https://git.kernel.org/stable/c/3d4f23885e4b90347c9a1d779af6e79a99b5172a
https://git.kernel.org/stable/c/df1d8abf36ca3681c21a6809eaa9a1e01ef897a6
reply other threads:[~2026-05-08 14:25 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=2026050852-CVE-2026-43436-9469@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