# CVE-2026-72007: pmdomain: imx: Fix i.MX8MP VC8000E power up sequence

> A timing issue in the i.MX8MP VC8000E power-up sequence can cause a system hang, 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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72007, DEBIAN-CVE-2026-72007, GHSA-4c88-c5vh-m8mh, UBUNTU-CVE-2026-72007

## What is CVE-2026-72007?

CVE-2026-72007 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:

pmdomain: imx: Fix i.MX8MP VC8000E power up sequence

Per errata[1]:
ERR050531: VPU_NOC power down handshake may hang during VC8000E/VPUMIX
power up/down cycling.
Description: VC8000E reset de-assertion edge and AXI clock may have a
timing issue.
Workaround: Set bit2 (vc8000e_clk_en) of BLK_CLK_EN_CSR to 0 to gate off
both AXI clock and VC8000E clock sent to VC8000E and AXI clock sent to
VPU_NOC m_v_2 interface during VC8000E power up(VC8000E reset is
de-asserted by HW)

Add a bool variable is_errata_err050531 in
'struct imx8m_blk_ctrl_domain_data' to represent whether the workaround
is needed. If is_errata_err050531 is true, first clear the clk before
powering up gpc, then enable the clk after powering up gpc.

[1] https://www.nxp.com/webapp/Download?colCode=IMX8MP_1P33A

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


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

Apply the vendor's patch.

## Is CVE-2026-72007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72007 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-72007 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-72007/ (Markdown: https://insights.sbomify.com/CVE-2026-72007/index.md)
```

## Sources

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

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