VulnerabilityPublished 17 Sep 2026Updated 30 Oct 2026

CVE-2026-93081: Linux kernel · firmware: arm_scmi: Fix SCMI device destroy lifetimes

Source GCVE Database

Compare

Authoritative record:CVE-2026-93081· Medium

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

Data as of 30 Oct 2026, 18:18 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in d8ecdceeb90cd2c265b222a7b65487faf68fea73, c59b3393df1348a12308aaabd5fbc58ed6b21cf5, afe5c022a180e0ade394d3fffbafc1a701f50993 +8

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-x6gc-qjww-67r2

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.1.138 <6.1.191 >=6.6.90 <6.6.160 >=6.12.28 <6.12.114 >=5.15.182 <5.16 >=6.14.6 <6.15	Fixed in d8ecdceeb90cd2c265b222a7b65487faf68fea73 c59b3393df1348a12308aaabd5fbc58ed6b21cf5 afe5c022a180e0ade394d3fffbafc1a701f50993 a60bc2df2d323cc1342f0cf95563cae266801e20 916e27f71a80f6d77c48d1a1a5782d6d5ef9017c 6abe8fe36b29ff51d1a42c2f338972883f4751a5 6.15 6.12.114 6.6.160 6.1.191 5.16
LinuxLinux	Affected =6.15	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to correct device reference handling and cleanup in the arm_scmi firmware driver. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation.

Description

A use-after-free vulnerability in the Linux kernel's arm_scmi firmware component was fixed by correcting device reference handling during SCMI device destruction. The flaw involved premature dropping of device references, which could lead to device release while still in use, and potential reuse of SCMI bus IDs before proper cleanup.

Impact

The flaw could lead to use-after-free conditions in the arm_scmi firmware driver within the Linux kernel, potentially causing system instability or crashes due to accessing freed device structures. There is no indication of remote exploitability or privilege escalation from the provided data. No known exploits in the wild have been reported.

Summary

The vulnerability in the Linux kernel's arm_scmi firmware driver was due to the scmi_child_dev_find() function dropping the reference obtained from device_find_child() too early. This allowed a concurrent device unregister operation to release the device while the destroy path was still using the pointer, risking use-after-free conditions. The fix ensures the reference is held until scmi_device_destroy() completes unregistering the child device. Additionally, device_unregister() was split in __scmi_device_destroy() to prevent SCMI bus IDs from being reused prematurely before sysfs cleanup. The final device release callback was also updated to handle cleanup paths consistently, preventing double freeing of SCMI bus IDs.

References

Community reviews

Loading reviews…