Bug 2536647 (CVE-2026-93184) - CVE-2026-93184 kernel: ASoC: fsl_audmix: rework runtime PM handling in probe
Summary: CVE-2026-93184 kernel: ASoC: fsl_audmix: rework runtime PM handling in probe
Keywords:
Status: NEW
Alias: CVE-2026-93184
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 19:01 UTC by OSIDB Bzimport
Modified: 2026-10-20 11:52 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 19:01:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.