Invalid kernel lock access via early Harmony interrupt
Published Sep 16, 2026 · Updated Sep 16, 2026
Race condition in the Linux Harmony ALSA driver allows a pending device interrupt to use uninitialized spinlocks during probe. In snd_harmony_create(), request_irq() exposes the handler before h->lock and h->mixer_lock are initialized, so an early IRQ reaches invalid lock state. Reachability requires PA-RISC Harmony audio hardware and a pending interrupt in the narrow driver-probe window; published material identifies neither an attacker-controlled trigger nor a specific failure mode.
Summary
What happened
Race condition in the Linux Harmony ALSA driver allows a pending device interrupt to use uninitialized spinlocks during probe. In snd_harmony_create(), request_irq() exposes the handler before h->lock and h->mixer_lock are initialized, so an early IRQ reaches invalid lock state. Reachability requires PA-RISC Harmony audio hardware and a pending interrupt in the narrow driver-probe window; published material identifies neither an attacker-controlled trigger nor a specific failure mode.
The record
- CVE
- CVE-2026-89980
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <33abb7491e89285a41565670945293dda841afc4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7dc239edb6d58e01c9ec868565cc03e7adf91747
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <89992bda7dfbba7ded2ba4185730453c57fa65bc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9347588bbd6ad43a85e17046d9c117a41453c52a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9af6c9203583655cb7ed45e52e14101652b37547
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cd209eb3136e002becbda232e399fa31a2276436
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f86ff9238b0c8284909e073a681a60708b9f36ab
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo