ASoC: fsl_audmix: rework runtime PM handling in probe (CVE-2026-93184) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93184

ASoC: fsl_audmix: rework runtime PM handling in probe

Answer in brief

CVE-2026-93184 records a Unknown severity vulnerability in ASoC: fsl_audmix: rework runtime PM handling in probe. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=be1df61cf06efb355c90702e46b8d46f055acb4e <b5c3f8015af442c2411722cf8c220cfbae271230 \|\| >=be1df61cf06efb355c90702e46b8d46f055acb4e <e921cc73fae68ccee932ad0a4fb11d637557db0e \|\| >=be1df61cf06efb355c90702e46b8d46f055acb4e <22c944e440bc9b16c4ee409943d69bb8ef575c9e \|\| >=be1df61cf06efb355c90702e46b8d46f055acb4e <3359ba93d01a23b2e4249e9e44ccfe48eb9c5d71	b5c3f8015af442c2411722cf8c220cfbae271230, e921cc73fae68ccee932ad0a4fb11d637557db0e, 22c944e440bc9b16c4ee409943d69bb8ef575c9e, 3359ba93d01a23b2e4249e9e44ccfe48eb9c5d71
Linux/Linuxgeneric	5.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to b5c3f8015af442c2411722cf8c220cfbae271230 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.