From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-39757: ALSA: usb-audio: Validate UAC3 cluster segment descriptors
Date: Thu, 11 Sep 2025 18:52:57 +0200 [thread overview]
Message-ID: <2025091144-CVE-2025-39757-e212@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Validate UAC3 cluster segment descriptors
UAC3 class segment descriptors need to be verified whether their sizes
match with the declared lengths and whether they fit with the
allocated buffer sizes, too. Otherwise malicious firmware may lead to
the unexpected OOB accesses.
The Linux kernel CVE team has assigned CVE-2025-39757 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 5.4.297 with commit 799c06ad4c9c790c265e8b6b94947213f1fb389c
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 5.10.241 with commit 786571b10b1ae6d90e1242848ce78ee7e1d493c4
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 5.15.190 with commit 275e37532e8ebe25e8a4069b2d9f955bfd202a46
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.1.149 with commit 47ab3d820cb0a502bd0074f83bb3cf7ab5d79902
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.6.103 with commit 1034719fdefd26caeec0a44a868bb5a412c2c1a5
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.12.43 with commit ae17b3b5e753efc239421d186cd1ff06e5ac296e
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.15.11 with commit dfdcbcde5c20df878178245d4449feada7d5b201
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.16.2 with commit 7ef3fd250f84494fb2f7871f357808edaa1fc6ce
Issue introduced in 4.19 with commit 11785ef53228d23ec386f5fe4a34601536f0c891 and fixed in 6.17-rc2 with commit ecfd41166b72b67d3bdeb88d224ff445f6163869
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-2025-39757
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/stream.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/799c06ad4c9c790c265e8b6b94947213f1fb389c
https://git.kernel.org/stable/c/786571b10b1ae6d90e1242848ce78ee7e1d493c4
https://git.kernel.org/stable/c/275e37532e8ebe25e8a4069b2d9f955bfd202a46
https://git.kernel.org/stable/c/47ab3d820cb0a502bd0074f83bb3cf7ab5d79902
https://git.kernel.org/stable/c/1034719fdefd26caeec0a44a868bb5a412c2c1a5
https://git.kernel.org/stable/c/ae17b3b5e753efc239421d186cd1ff06e5ac296e
https://git.kernel.org/stable/c/dfdcbcde5c20df878178245d4449feada7d5b201
https://git.kernel.org/stable/c/7ef3fd250f84494fb2f7871f357808edaa1fc6ce
https://git.kernel.org/stable/c/ecfd41166b72b67d3bdeb88d224ff445f6163869
reply other threads:[~2025-09-11 16:54 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=2025091144-CVE-2025-39757-e212@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.