# CVE-2026-93080: firmware: arm_scmi: Fix transport device teardown lookup

> A flaw in the Linux kernel SCMI driver allows malformed firmware to cause a denial of service during device teardown.

- **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:** BELL-CVE-2026-93080, DEBIAN-CVE-2026-93080, GHSA-mj5f-93r8-jjjp, UBUNTU-CVE-2026-93080

## What is CVE-2026-93080?

CVE-2026-93080 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:

firmware: arm_scmi: Fix transport device teardown lookup

SCMI transport devices are deliberately excluded from normal SCMI bus
matching so protocol drivers cannot bind to the internal transport
children. However, scmi_device_destroy() uses the same protocol/name
lookup to find devices that must be unregistered during channel teardown.

Split the match helper so driver matching still skips transport devices,
while explicit child lookup can find them for teardown. Use a shared
transport-device name prefix macro for both matching and name generation.

Since transport-device names are derived from direction and protocol ID,
reject duplicate protocol channel setup before creating or finding a
transport device. This prevents malformed firmware with duplicate
protocol child nodes from reusing an existing transport device and then
destroying it when the duplicate IDR insertion fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-93080 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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