# CVE-2026-80750: pmdomain: mediatek: fix remaining %pOF after of_node_put()

> A use-after-free vulnerability in the Linux kernel's MediaTek power domain driver allows attackers to cause a denial of service or potentially execute code via crafted device tree interactions.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80750, DEBIAN-CVE-2026-80750, GHSA-r977-99pr-5gm5, UBUNTU-CVE-2026-80750

## What is CVE-2026-80750?

CVE-2026-80750 is a high-severity use after free 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: fix remaining %pOF after of_node_put()

scpsys_get_bus_protection_legacy() looks up several legacy bus
protection regmaps from device-tree nodes.

Two error paths put the device node before checking whether the regmap
lookup failed, but still pass that node to dev_err_probe() with %pOF on
failure. If of_node_put() drops the last reference, the later %pOF
formatting can dereference a freed device node.

Keep the node reference until after the error message has been emitted in
the infracfg and SMI lookup paths. Also drop the SMI node before
returning when the SMI phandle is missing.

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


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

Apply the vendor's patch.

## Is CVE-2026-80750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80750 is a high-severity use after free 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-80750 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-80750/ (Markdown: https://insights.sbomify.com/CVE-2026-80750/index.md)
```

## Sources

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

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