CVE-2026-80967
Description
A flaw was found in the ALSA pcxhr driver within the Linux kernel. The pcxhr_probe() function requests a threaded interrupt before properly initializing a critical mutex (mgr->lock). This oversight could allow an early interrupt to operate on an uninitialized mutex, potentially leading to system instability or a denial of service (DoS) condition. A local attacker could potentially exploit this to impact system availability.
Statement
This low-impact flaw in the Linux kernel ALSA pcxhr driver affects Red Hat Enterprise Linux (kernel and kernel-rt) and the OpenShift Container Platform RHCOS images that ship the kernel. The pcxhr_probe() function registers a threaded interrupt handler before initializing the mgr->lock mutex that the handler takes, so an early interrupt during device probe can run against uninitialized mutex state. The consequence is limited to system availability: system instability or a kernel panic during probing of the affected audio hardware, i.e. a local denial of service. Reliable exploitation is difficult because it requires winning the race between interrupt delivery and mutex initialization during driver probe on a system with the hardware present. Red Hat rates this flaw Low severity (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), while the upstream CVEORG rating is 8.4 (IMPORTANT); the difference reflects Red Hat's assessment that only availability is impacted and that the probe-time race is hard to trigger deterministically. Fixes for the affected Red Hat Enterprise Linux and OpenShift streams are deferred because the flaw falls below the severity threshold used to file fix trackers, leaving a residual, low-likelihood risk of probe-time system instability on systems with the affected hardware.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 8.4 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
If a resource is not initialized, it could contain unpredictable or expired data, or it could be initialized to defaults that are invalid. This can have security implications when the resource is expected to have certain properties or values.
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.