# CVE-2026-93184: ASoC: fsl_audmix: rework runtime PM handling in probe

> A flaw in the Linux kernel's fsl_audmix driver causes a system hang when register writes occur before hardware power-up during probe.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102801, BELL-CVE-2026-93184, DEBIAN-CVE-2026-93184, GHSA-88wf-2wr7-wjcj, UBUNTU-CVE-2026-93184

## What is CVE-2026-93184?

CVE-2026-93184 is a denial of service vulnerability in Linux, published on 17 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: fsl_audmix: rework runtime PM handling in probe

After pm_runtime_enable() the AUDMIX block is powered off and stays
suspended until the first runtime resume. Register writes issued between
probe() and the first resume (e.g. from DAPM or ALSA control paths)
target unpowered hardware and cause a system hang.

Fix this by calling pm_runtime_resume_and_get() immediately after
pm_runtime_enable() to power the hardware up and enable its clocks.
Release the reference afterwards with pm_runtime_put() to allow the
runtime PM framework to suspend the device and switch the regmap to
cache-only mode when idle.

When CONFIG_PM is disabled or runtime PM is not enabled, pm_runtime_*
calls are stubs that do not power up the hardware. Handle this case
explicitly by calling fsl_audmix_runtime_resume() directly so the
hardware is always initialised and its clocks are enabled, ensuring
register accesses succeed regardless of PM configuration.

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


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

Apply the vendor's patch.

## Is CVE-2026-93184 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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