# CVE-2026-90238: media: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path

> A self-deadlock in the AMD ISP4 driver error path causes a system hang when initialization fails, requiring a kernel patch.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-gwc7-3f3j-839g, UBUNTU-CVE-2026-90238

## What is CVE-2026-90238?

CVE-2026-90238 is a denial of service vulnerability in Linux, published on 17 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:

media: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path

isp4sd_pwron_and_init() holds ops_mutex via guard(mutex) and, on any
init failure, jumps to err_deinit and calls isp4sd_pwroff_and_deinit().
That helper takes the same ops_mutex, re-acquiring a non-recursive mutex
already held by the current thread, so any init failure deadlocks.

Unwind the error path in stages instead, releasing only what each
failure point acquired. This also avoids the issues that an
unconditional teardown would hit at the earlier failures, such as a
runtime-PM underflow from pm_runtime_resume_and_get() and MMIO access
while the device is unpowered.

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


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

Apply the vendor's patch.

## Is CVE-2026-90238 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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