# CVE-2026-72009: pmdomain: imx93-blk-ctrl: Extract PHY as shared domain for DSI/CSI

> A race condition in the i.MX93 block control driver allows disabling shared MIPI PHY resources while active, potentially causing system instability or denial of service.

- **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:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-72009, DEBIAN-CVE-2026-72009, GHSA-7wvh-6fjm-x43j, UBUNTU-CVE-2026-72009

## What is CVE-2026-72009?

CVE-2026-72009 is a high-severity 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: imx93-blk-ctrl: Extract PHY as shared domain for DSI/CSI

The MIPI DSI and CSI domains share control bits for clock and reset, which
can lead to incorrect behavior if one domain disables the shared resource
while the other is still active.

To fix the issue, introduce a shared MIPI PHY power domain to own the
common resources and make DSI and CSI its subdomains. This ensures the
shared bits are properly managed and not disabled while still in use.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

Apply the vendor's patch.

## Is CVE-2026-72009 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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