VulnerabilityPublished 17 Sep 2026Updated 6 Oct 2026

CVE-2026-93082: Linux kernel · firmware: arm_scmi: Unwind P2A receiver mailbox setup failure

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-93082· Low

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Low

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.

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

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been applied to the Linux kernel to properly release the primary mailbox channel on failure during P2A receiver mailbox setup. Users should update to patched kernel versions to resolve this issue. Since this is a kernel-level fix, applying official kernel updates from the Linux distribution vendor is the recommended remediation.

Description

A vulnerability in the Linux kernel's arm_scmi firmware component related to the P2A receiver mailbox setup has been resolved. The issue occurs when mailbox_chan_setup() requests an additional P2A receiver channel after successfully acquiring the primary channel; if the additional request fails, the primary channel remains allocated improperly. This can cause the primary mailbox channel to stay busy, potentially affecting probe deferral or other setup processes. The fix ensures the primary channel is properly released on failure.

Impact

The improper release of the primary P2A receiver mailbox channel can lead to resource allocation issues during device probe or setup, potentially causing failures in hardware initialization or communication. While no direct exploitation or active attacks are known, this could affect system stability or hardware functionality on affected Linux kernel versions.

Summary

The vulnerability in the Linux kernel firmware arm_scmi component involves improper handling of mailbox channel allocation during the P2A receiver mailbox setup. Specifically, mailbox_chan_setup() may allocate a primary P2A channel successfully, then attempt to allocate an additional channel. If the second allocation fails, the function returns without releasing the primary channel, leaving it busy and potentially causing issues with probe deferral or subsequent setup attempts. The patch corrects this by unwinding the primary mailbox channel allocation before returning an error, preventing resource leakage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 23:29 UTC

Technical details

References

Community reviews

Related threats