# CVE-2026-97909: ASoC: sti: initialize IRQ lock before requesting IRQ

> A race condition in the Linux kernel STI audio driver allows a local attacker to cause a denial of service by triggering an interrupt before the lock is initialized.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104580, BELL-CVE-2026-97909, DEBIAN-CVE-2026-97909, GHSA-7jmc-77v8-c6vf, UBUNTU-CVE-2026-97909

## What is CVE-2026-97909?

CVE-2026-97909 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: sti: initialize IRQ lock before requesting IRQ

uni_reader_init() registers the shared IRQ before initializing
reader->irq_lock. A pending interrupt can invoke the handler while the
lock is still uninitialized.

Initialize the lock before registering the IRQ so the interrupt path
always sees valid lock state.

## Which versions are affected by CVE-2026-97909?


## How do I fix CVE-2026-97909?

Apply the vendor's patch.

## Is CVE-2026-97909 being exploited?

There is no known exploitation of CVE-2026-97909 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97909 and fix it if it is affected.

What it is: CVE-2026-97909 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97909 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97909/ (Markdown: https://insights.sbomify.com/CVE-2026-97909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97909
- OSV: https://osv.dev/vulnerability/CVE-2026-97909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97909/
Summaries are generated and may contain mistakes; the official description above is the record.