From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72445: ALSA: usb-audio: qcom: clear opened when stream enable fails
Date: Sat, 15 Aug 2026 15:08:44 +0900 [thread overview]
Message-ID: <2026081530-CVE-2026-72445-e0bc@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: qcom: clear opened when stream enable fails
On enable, subs->opened is set before the service_interval is validated;
an invalid interval jumps to the response label without clearing it, so
the substream is wedged at -EBUSY until a disable or disconnect.
Clear subs->opened on the enable error path.
The Linux kernel CVE team has assigned CVE-2026-72445 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 326bbc348298ab0946c5560defe024a5f6ef28bb and fixed in 6.18.40 with commit 53c23d56b46b1ae51574d92110895086aead7ad7
Issue introduced in 6.16 with commit 326bbc348298ab0946c5560defe024a5f6ef28bb and fixed in 7.1.5 with commit ec6fb1ecada8ddfc3d0e1728e4792d16ae55dcdb
Issue introduced in 6.16 with commit 326bbc348298ab0946c5560defe024a5f6ef28bb and fixed in 7.2-rc1 with commit 3c7af07943b2718087ae791cad450af5cf646d90
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-72445
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/qcom/qc_audio_offload.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/53c23d56b46b1ae51574d92110895086aead7ad7
https://git.kernel.org/stable/c/ec6fb1ecada8ddfc3d0e1728e4792d16ae55dcdb
https://git.kernel.org/stable/c/3c7af07943b2718087ae791cad450af5cf646d90
reply other threads:[~2026-08-15 6:28 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=2026081530-CVE-2026-72445-e0bc@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.