Probe failure via leaked receiver mailbox
Published Sep 17, 2026 · Updated Sep 17, 2026
Linux 6.11 ARM SCMI mailbox resource leakage allows attackers to block later driver probe attempts via a receiver setup failure. The mailbox_chan_setup() function returns after an additional P2A receiver request fails without releasing the primary channel already allocated. The failure requires the ARM SCMI mailbox transport and that setup error; attacker control of the error is undocumented, and the reported consequence is a busy channel rather than a kernel crash.
Summary
What happened
Linux 6.11 ARM SCMI mailbox resource leakage allows attackers to block later driver probe attempts via a receiver setup failure. The mailbox_chan_setup() function returns after an additional P2A receiver request fails without releasing the primary channel already allocated. The failure requires the ARM SCMI mailbox transport and that setup error; attacker control of the error is undocumented, and the reported consequence is a busy channel rather than a kernel crash.
The record
- CVE
- CVE-2026-93082
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.11
- Affected versionversion=fa8b28ba22d95be4d2dd3c37fbdbdc066af82941 <3515aed7fe424b79c49ff9cd51f7802a64a4ab7b
- Affected versionversion=fa8b28ba22d95be4d2dd3c37fbdbdc066af82941 <3b0b02134ab90202af80b102fa37196b9689e86f
- Affected versionversion=fa8b28ba22d95be4d2dd3c37fbdbdc066af82941 <4c2a5d72357e5c6743c23b59615da287140d9d31
- Affected versionversion=fa8b28ba22d95be4d2dd3c37fbdbdc066af82941 <f3e3773c4e5e96549d7540d8ddeb4fcd534f6f1d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started