# CVE-2026-72260: ASoC: mediatek: mt8192: Check runtime resume during probe

> A missing error check in the MT8192 audio driver probe can cause a PM usage count leak, potentially leading to denial of service.

- **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:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72260, DEBIAN-CVE-2026-72260, GHSA-g833-2rhh-96rv, UBUNTU-CVE-2026-72260

## What is CVE-2026-72260?

CVE-2026-72260 is a denial of service vulnerability in Linux, published on 15 Aug 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: mediatek: mt8192: Check runtime resume during probe

The MT8192 AFE probe enables runtime PM temporarily while reinitializing
the regmap cache from hardware, but it uses pm_runtime_get_sync()
without checking the return value. If runtime resume fails, probe keeps
going without the device necessarily being accessible, and
pm_runtime_get_sync() may leave the PM usage count incremented.

The regmap_reinit_cache() failure path also returns before dropping the
temporary PM reference and before clearing pm_runtime_bypass_reg_ctl.

Use pm_runtime_resume_and_get() so resume failures do not leak a usage
count, and clear the temporary bypass flag after dropping the probe PM
reference on all regmap_reinit_cache() outcomes.

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


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

Apply the vendor's patch.

## Is CVE-2026-72260 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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