# CVE-2026-99089: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111122, BELL-CVE-2026-99089, DEBIAN-CVE-2026-99089, GHSA-xc7f-3c97-gfm9, UBUNTU-CVE-2026-99089

## What is CVE-2026-99089?

CVE-2026-99089 is a vulnerability in Linux, published on 26 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM

The probe function puts the device into the runtime PM active state with
only the "iis" bus clock enabled, but it also sets priv->op_clk to the
parent of the RCLK_SRC mux without enabling it. The runtime PM suspend
callback disables both clocks, so the first runtime suspend after probe
disables op_clk once more than it was enabled.

On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate,
so this triggers the following warning during boot:

 WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45
 i2s_bus already disabled
 ...
 Workqueue: pm pm_runtime_work
 Call trace:
  ...
  clk_core_disable from clk_disable+0x28/0x34
  clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]
  i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298
  genpd_runtime_suspend from __rpm_callback+0x48/0x18c
  __rpm_callback from rpm_callback+0x4c/0x50
  rpm_callback from rpm_suspend+0xf4/0x718
  rpm_suspend from pm_runtime_work+0x9c/0xa0
  ...

Fix this by enabling op_clk in probe right after getting it, so the clock
state matches the runtime PM active state, and by disabling it in remove.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99089 is a vulnerability in Linux, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99089 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-99089/ (Markdown: https://insights.sbomify.com/CVE-2026-99089/index.md)
```

## Sources

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

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