# CVE-2026-90213: firewire: core: fix memory leak in error path of build_tree()

> A memory leak in the Linux kernel's firewire subsystem allows local attackers to cause denial of service by triggering error paths in build_tree().

- **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:** 21 Oct 2026
- **Also known as:** AZL-102359, BELL-CVE-2026-90213, DEBIAN-CVE-2026-90213, GHSA-584h-rw5g-vhjq, UBUNTU-CVE-2026-90213

## What is CVE-2026-90213?

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

firewire: core: fix memory leak in error path of build_tree()

In the error path of build_tree(), node instances can remain in the local
linked list when the function returns.

Whenever an invalid value is detected in the self ID sequence, each
allocated node instance is either an entry in the linked list or an
entry in the ports array of its parent node. Therefore, the allocate
node instances can be safely released by traversing the linked list from
its head.

Release the remaining node instances with for_each_fw_node() before
returning to the caller.

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


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

Apply the vendor's patch.

## Is CVE-2026-90213 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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