Answer in brief
CVE-2026-93084 records a Unknown severity vulnerability in firmware: arm_scmi: Drop handle on protocol bind failures. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=971fc0665f1361f23251e4d85fac4aed1b683505 <0f860db24ee95e5da4866303a35e55098b9641b3 || >=971fc0665f1361f23251e4d85fac4aed1b683505 <df273eced7cec550465fd1bb82a5d2c3c7d3c437 || >=971fc0665f1361f23251e4d85fac4aed1b683505 <a54dc23e8bd2246c28eafffa60b4634f0d1a11cc || >=971fc0665f1361f23251e4d85fac4aed1b683505 <77d2985d1e80e67f32026fc03e975c4c83cc543d || >=971fc0665f1361f23251e4d85fac4aed1b683505 <e3a5c30d233ca5d3e799a80da806554c703bda13 | 0f860db24ee95e5da4866303a35e55098b9641b3, df273eced7cec550465fd1bb82a5d2c3c7d3c437, a54dc23e8bd2246c28eafffa60b4634f0d1a11cc, 77d2985d1e80e67f32026fc03e975c4c83cc543d, e3a5c30d233ca5d3e799a80da806554c703bda13 |
| Linux/Linuxgeneric | 6.3 | Not reported |
| Linux/Linuxgeneric | >=b50c9270304cfed6ee1c4ce5036102ad7b762051 <b5377e690cd4fe87ee52fcf067c9929414ea8f4e || >=971fc0665f1361f23251e4d85fac4aed1b683505 <0f860db24ee95e5da4866303a35e55098b9641b3 || >=971fc0665f1361f23251e4d85fac4aed1b683505 <df273eced7cec550465fd1bb82a5d2c3c7d3c437 || >=971fc0665f1361f23251e4d85fac4aed1b683505 <a54dc23e8bd2246c28eafffa60b4634f0d1a11cc || >=971fc0665f1361f23251e4d85fac4aed1b683505 <77d2985d1e80e67f32026fc03e975c4c83cc543d || >=971fc0665f1361f23251e4d85fac4aed1b683505 <e3a5c30d233ca5d3e799a80da806554c703bda13 | b5377e690cd4fe87ee52fcf067c9929414ea8f4e, 0f860db24ee95e5da4866303a35e55098b9641b3, df273eced7cec550465fd1bb82a5d2c3c7d3c437, a54dc23e8bd2246c28eafffa60b4634f0d1a11cc, 77d2985d1e80e67f32026fc03e975c4c83cc543d, e3a5c30d233ca5d3e799a80da806554c703bda13 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 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: Drop handle on protocol bind failures The SCMI bus notifier acquires an SCMI handle when the driver core emits BUS_NOTIFY_BIND_DRIVER, before invoking the protocol driver probe callback. The protocol probe path only checks whether sdev->handle is set. If device_link_add() fails after the handle has been acquired, the protocol device can still bind with a valid handle but without the dependency link to the SCMI parent. A concurrent parent unbind can then miss the child and tear down the SCMI instance while the child still holds a handle into it. If the protocol driver probe later fails, for example with -EPROBE_DEFER, the driver core emits BUS_NOTIFY_DRIVER_NOT_BOUND rather than BUS_NOTIFY_UNBOUND_DRIVER. The SCMI notifier only released the handle on BUS_NOTIFY_UNBOUND_DRIVER, so each failed protocol-device bind leaked the SCMI instance users refcount and left sdev->handle set after the failed probe. Make the link helper report failure and drop the acquired handle if the link cannot be created. Also handle BUS_NOTIFY_DRIVER_NOT_BOUND in the same cleanup path used for unbind so failed probes balance the earlier BUS_NOTIFY_BIND_DRIVER acquisition.
Quoted source text, attributed separately from HOL analysis.