CVE-2026-93084

published 17 Sep 2026 · updated 20 Nov 2026

firmware: arm_scmi: Drop handle on protocol bind failures

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b5377e690cd4fe87ee52fcf067c9929414ea8f4e, Kernel 77d2985d1e80e67f32026fc03e975c4c83cc543d, Kernel a54dc23e8bd2246c28eafffa60b4634f0d1a11cc and 7 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=b50c9270304cfed6ee1c4ce5036102ad7b762051 <b5377e690cd4fe87ee52fcf067c9929414ea8f4e, >=971fc0665f1361f23251e4d85fac4aed1b683505 <77d2985d1e80e67f32026fc03e975c4c83cc543d, >=971fc0665f1361f23251e4d85fac4aed1b683505 <a54dc23e8bd2246c28eafffa60b4634f0d1a11cc, >=971fc0665f1361f23251e4d85fac4aed1b683505 <df273eced7cec550465fd1bb82a5d2c3c7d3c437, >=971fc0665f1361f23251e4d85fac4aed1b683505 <e3a5c30d233ca5d3e799a80da806554c703bda13, =6.3, >=971fc0665f1361f23251e4d85fac4aed1b683505 <0f860db24ee95e5da4866303a35e55098b9641b3b5377e690cd4fe87ee52fcf067c9929414ea8f4e, 77d2985d1e80e67f32026fc03e975c4c83cc543d, a54dc23e8bd2246c28eafffa60b4634f0d1a11cc, df273eced7cec550465fd1bb82a5d2c3c7d3c437, e3a5c30d233ca5d3e799a80da806554c703bda13, 0f860db24ee95e5da4866303a35e55098b9641b3
linux-kernel: Kernel>=6.19.0 <7.2.6, >=6.3.0 <6.6.157, >=6.7.0 <6.12.110, >=6.13.0 <6.18.527.2.6, 6.6.157, 6.12.110, 6.18.52

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93084 severity on Zeptric[![CVE-2026-93084](https://zeptric.io/badge/cve/CVE-2026-93084.svg)](https://zeptric.io/cve/CVE-2026-93084)