Answer in brief
CVE-2026-93080 records a Unknown severity vulnerability in firmware: arm_scmi: Fix transport device teardown lookup. 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 | >=9593804c44c24545e1b0496786dcb765d7b0e193 <c656427440ea627166394d00c4b72147d5d79c60 || >=9593804c44c24545e1b0496786dcb765d7b0e193 <4635953b4c1af477e166073521a77de6279f6929 || >=9593804c44c24545e1b0496786dcb765d7b0e193 <a14dd8fe0a95db638c550ed984cfe2a7428c783d | c656427440ea627166394d00c4b72147d5d79c60, 4635953b4c1af477e166073521a77de6279f6929, a14dd8fe0a95db638c550ed984cfe2a7428c783d |
| Linux/Linuxgeneric | 6.16 | 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: 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.
Quoted source text, attributed separately from HOL analysis.