# CVE-2026-80751: pmdomain: mediatek: mfg: initialize prev_o in mtk_mfg_attach_dev()

> An uninitialized pointer in the MediaTek MFG power domain driver can cause a kernel crash or logic error during device attachment.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-80751, GHSA-3f8w-94vm-5g9p, UBUNTU-CVE-2026-80751

## What is CVE-2026-80751?

CVE-2026-80751 is a high-severity vulnerability in Linux, published on 3 Sep 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:

pmdomain: mediatek: mfg: initialize prev_o in mtk_mfg_attach_dev()

mtk_mfg_attach_dev() reads prev_o on the first iteration of its loop,
in "if (prev_o && prev_o->freq == o->freq)", before prev_o is assigned
at the end of the loop body. On that first iteration, evaluating prev_o
reads an indeterminate value. If it is non-NULL, the condition
dereferences a stale or invalid pointer, potentially faulting or
incorrectly skipping the first OPP.

Initialize prev_o to NULL. This matches the intent as well: there is no
previous OPP to compare against on the first iteration.

Found with Clang's -Wconditional-uninitialized.

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


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

Apply the vendor's patch.

## Is CVE-2026-80751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80751 is a high-severity vulnerability in Linux, published on 3 Sep 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-80751 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-80751/ (Markdown: https://insights.sbomify.com/CVE-2026-80751/index.md)
```

## Sources

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

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