# CVE-2026-90402: bus: mhi: host: Fix controller cleanup on EDL sysfs failure

> Improper cleanup in the Linux kernel MHI host driver when sysfs creation fails, potentially leaving a registered device in an inconsistent state.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90402, DEBIAN-CVE-2026-90402, GHSA-fqr5-r6rr-x7fx, UBUNTU-CVE-2026-90402

## What is CVE-2026-90402?

CVE-2026-90402 is a high-severity 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: host: Fix controller cleanup on EDL sysfs failure

mhi_register_controller() adds the controller device before creating the
optional trigger_edl sysfs file. If sysfs_create_file() fails, the error
path only drops the device reference and leaves the device registered.

Hence, call device_del() in the error path before put_device().

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


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

Apply the vendor's patch.

## Is CVE-2026-90402 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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