Answer in brief
CVE-2026-90213 records a Unknown severity vulnerability in firewire: core: fix memory leak in error path of build_tree(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3038e353cfaf548eb94f02b172b9dbe412abd24c <848eaef4d30b385eb074214b7fa58287506158ad || >=3038e353cfaf548eb94f02b172b9dbe412abd24c <d6037e42aa4dd29bb9d9f67ef438128c5bfe3448 || >=3038e353cfaf548eb94f02b172b9dbe412abd24c <6a990e74d4e848f32eda91d69e4f885604fc326d || >=3038e353cfaf548eb94f02b172b9dbe412abd24c <05bfb1327dc5fb61528bab31cd8f0c1e4bddec23 | 848eaef4d30b385eb074214b7fa58287506158ad, d6037e42aa4dd29bb9d9f67ef438128c5bfe3448, 6a990e74d4e848f32eda91d69e4f885604fc326d, 05bfb1327dc5fb61528bab31cd8f0c1e4bddec23 |
| Linux/Linuxgeneric | 2.6.22 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.