VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93084: Linux kernel · firmware: arm_scmi: Drop handle on protocol bind failures

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in e3a5c30d233ca5d3e799a80da806554c703bda13 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e3a5c30d233ca5d3e799a80da806554c703bda13, df273eced7cec550465fd1bb82a5d2c3c7d3c437, a54dc23e8bd2246c28eafffa60b4634f0d1a11cc +2

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 971fc0665f1361f23251e4d85fac4aed1b683505, < e3a5c30d233ca5d3e799a80da806554c703bda13	Fixed in e3a5c30d233ca5d3e799a80da806554c703bda13
LinuxLinux	Affected ≥ 971fc0665f1361f23251e4d85fac4aed1b683505, < df273eced7cec550465fd1bb82a5d2c3c7d3c437	Fixed in df273eced7cec550465fd1bb82a5d2c3c7d3c437
LinuxLinux	Affected ≥ 971fc0665f1361f23251e4d85fac4aed1b683505, < a54dc23e8bd2246c28eafffa60b4634f0d1a11cc	Fixed in a54dc23e8bd2246c28eafffa60b4634f0d1a11cc
LinuxLinux	Affected ≥ 971fc0665f1361f23251e4d85fac4aed1b683505, < 77d2985d1e80e67f32026fc03e975c4c83cc543d	Fixed in 77d2985d1e80e67f32026fc03e975c4c83cc543d
LinuxLinux	Affected ≥ 971fc0665f1361f23251e4d85fac4aed1b683505, < 0f860db24ee95e5da4866303a35e55098b9641b3	Fixed in 0f860db24ee95e5da4866303a35e55098b9641b3
LinuxLinux	Affected =6.3	Fixed in–

Description

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.

References

Community reviews

Loading reviews…