- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b50c9270304cfed6ee1c4ce5036102ad7b762051 – < b5377e690cd4fe87ee52fcf067c9929414ea8f4e
- affected 971fc0665f1361f23251e4d85fac4aed1b683505 – < 0f860db24ee95e5da4866303a35e55098b9641b3
- affected 971fc0665f1361f23251e4d85fac4aed1b683505 – < df273eced7cec550465fd1bb82a5d2c3c7d3c437
- affected 971fc0665f1361f23251e4d85fac4aed1b683505 – < a54dc23e8bd2246c28eafffa60b4634f0d1a11cc
- affected 971fc0665f1361f23251e4d85fac4aed1b683505 – < 77d2985d1e80e67f32026fc03e975c4c83cc543d
- affected 971fc0665f1361f23251e4d85fac4aed1b683505 – < e3a5c30d233ca5d3e799a80da806554c703bda13
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b5377e690cd4fe87ee52fcf067c9929414ea8f4e (opens in a new tab)
- https://git.kernel.org/stable/c/0f860db24ee95e5da4866303a35e55098b9641b3 (opens in a new tab)
- https://git.kernel.org/stable/c/df273eced7cec550465fd1bb82a5d2c3c7d3c437 (opens in a new tab)
- https://git.kernel.org/stable/c/a54dc23e8bd2246c28eafffa60b4634f0d1a11cc (opens in a new tab)
- https://git.kernel.org/stable/c/77d2985d1e80e67f32026fc03e975c4c83cc543d (opens in a new tab)
- https://git.kernel.org/stable/c/e3a5c30d233ca5d3e799a80da806554c703bda13 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82194 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93084)Record last updated .