# CVE-2026-89945: ASoC: cs35l34: drain threaded IRQ before runtime suspend

> A race condition in the Linux kernel cs35l34 audio codec driver allows a local attacker to cause a denial of service by triggering a use-after-free scenario during runtime suspend.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101454, BELL-CVE-2026-89945, DEBIAN-CVE-2026-89945, GHSA-w3mv-pmf4-r863, UBUNTU-CVE-2026-89945

## What is CVE-2026-89945?

CVE-2026-89945 is a vulnerability in Linux, published on 16 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: cs35l34: drain threaded IRQ before runtime suspend

cs35l34_runtime_suspend() currently switches the codec into
regcache_cache_only(true), asserts reset low, and powers the device off
without first quiescing the threaded IRQ registered by
devm_request_threaded_irq(). That leaves a window where
cs35l34_irq_thread() can still run after suspend has removed live
hardware access.

A running system can reach this during runtime PM while the driver still
has critical fault IRQs unmasked. If the threaded handler runs in that
window, it reads volatile INT_STATUS_1..4 after cache_only has been
enabled, ignores the regmap_read() failures, and can still execute the
PROT_RELEASE_CTL release sequence or the BST fault power-down writes.

Use disable_irq() before entering cache_only/reset-low/power-off so any
in-flight threaded handler is drained and no new IRQ thread can run
while the device is suspended. Re-enable the IRQ only after
runtime_resume() has restored live register access with regcache_sync().
Since probe only logs request_threaded_irq() failures and keeps going,
track whether the IRQ was actually installed before disabling or
re-enabling it.

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


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

Apply the vendor's patch.

## Is CVE-2026-89945 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89945 is a vulnerability in Linux, published on 16 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-89945 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-89945/ (Markdown: https://insights.sbomify.com/CVE-2026-89945/index.md)
```

## Sources

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

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