From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80967: ALSA: pcxhr: initialize mutexes before requesting threaded IRQ
Date: Fri, 11 Sep 2026 21:41:13 +0200 [thread overview]
Message-ID: <2026091143-CVE-2026-80967-156e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: pcxhr: initialize mutexes before requesting threaded IRQ
pcxhr_probe() requests pcxhr_threaded_irq() before initializing
mgr->lock, even though the threaded handler takes that mutex.
Initialize the manager locks before request_threaded_irq() so an
early interrupt cannot run against uninitialized mutex state during
probe.
The Linux kernel CVE team has assigned CVE-2026-80967 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.18 with commit 9bef72bdb26e291d6dffb04768741a0e49582666 and fixed in 6.12.109 with commit c069b3cfd753d6688ea0271c43553631ab38ce10
Issue introduced in 3.18 with commit 9bef72bdb26e291d6dffb04768741a0e49582666 and fixed in 6.18.50 with commit 7ef9ad82d95dd3c74570d80a689a0570fbc7539e
Issue introduced in 3.18 with commit 9bef72bdb26e291d6dffb04768741a0e49582666 and fixed in 7.2.4 with commit 7cf280fbef5db6310e1b32074c8c34d1ba459796
Issue introduced in 3.18 with commit 9bef72bdb26e291d6dffb04768741a0e49582666 and fixed in 7.3-rc1 with commit 6c97817e20598e5473094e0e38d1f51f1cf4dfff
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-80967
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/pcxhr/pcxhr.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/c069b3cfd753d6688ea0271c43553631ab38ce10
https://git.kernel.org/stable/c/7ef9ad82d95dd3c74570d80a689a0570fbc7539e
https://git.kernel.org/stable/c/7cf280fbef5db6310e1b32074c8c34d1ba459796
https://git.kernel.org/stable/c/6c97817e20598e5473094e0e38d1f51f1cf4dfff
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=2026091143-CVE-2026-80967-156e@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.