# CVE-2026-93136: bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation

> A refcount leak in the Linux kernel MHI endpoint driver can cause memory exhaustion and denial of service when device creation fails.

- **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:** AZL-102050, BELL-CVE-2026-93136, DEBIAN-CVE-2026-93136, GHSA-4w2p-3v8x-m8hh, UBUNTU-CVE-2026-93136

## What is CVE-2026-93136?

CVE-2026-93136 is a memory corruption 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:

bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation

mhi_ep_create_device() takes one device reference for the UL channel and
another for the DL channel after allocating the transfer device. These
references are normally released by mhi_ep_destroy_device() before the
device itself is removed.

If dev_set_name() or device_add() fails, the error path currently drops
only one reference. The remaining channel references keep the device
from being released and leave the channels associated with a device that
was never registered.

Route both failures through a common unwind path that drops the DL
channel reference, the UL channel reference, and the initial reference
from device_initialize().

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


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

Apply the vendor's patch.

## Is CVE-2026-93136 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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