CVE-2026-89980

Description

A flaw was found in the Linux kernel's ALSA (Advanced Linux Sound Architecture) Harmony driver. The snd_harmony_create() function registers an Interrupt Request (IRQ) before properly initializing associated locks. This allows a pending interrupt to invoke the handler while these locks are in an uninitialized state. Consequently, the system may experience instability or a denial of service.

Statement

This vulnerability is rated with a Moderate severity impact because an uninitialized lock state during device initialization could allow a race condition leading to kernel instability or local denial of service. The flaw resides exclusively within the Harmony sound driver developed for the PA-RISC architecture, a hardware platform that is not supported by Red Hat Enterprise Linux. Consequently, the vulnerable code is not built or shipped in Red Hat products, and supported releases are not affected.

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 HatNVDcve.org
Base Score5.5N/A8.4
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

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)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.