# CVE-2026-93225: phy: fsl-imx8mq-usb: fix typec switch leak on probe error path

> A memory leak in the Linux kernel USB PHY driver can lead to resource exhaustion and denial of service if probe fails.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/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:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93225, DEBIAN-CVE-2026-93225, GHSA-x24p-xpmf-j8m7, UBUNTU-CVE-2026-93225

## What is CVE-2026-93225?

CVE-2026-93225 is a high-severity memory corruption vulnerability in Linux, published on 24 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:

phy: fsl-imx8mq-usb: fix typec switch leak on probe error path

If probe fails after imx95_usb_phy_get_tca() succeeds, the typec
switch leaks because the only cleanup path was in .remove(), which
never runs on probe failure.

Use devm_add_action_or_reset() so the switch is cleaned up on both
probe failure and driver removal. The imx95_usb_phy_put_tca() is no
longer needed, it will be removed in .remove() too.

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


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

Apply the vendor's patch.

## Is CVE-2026-93225 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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