# CVE-2026-92506: firmware: arm_scmi: Fix requested device removal race

> A race condition in the Linux kernel SCMI driver allows concurrent unregistration to cause a use-after-free, potentially leading to system crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101864, BELL-CVE-2026-92506, DEBIAN-CVE-2026-92506, GHSA-5f27-8j35-25fh, UBUNTU-CVE-2026-92506

## What is CVE-2026-92506?

CVE-2026-92506 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

firmware: arm_scmi: Fix requested device removal race

scmi_protocol_device_unrequest() drops scmi_requested_devices_mtx while
notifying listeners but continues to retain the per-protocol list head.
When two SCMI drivers for the same protocol unregister concurrently, one
thread can remove the final request and free the list head while the other
is running its notifier. The latter then dereferences the freed list head
after reacquiring the mutex and can free it a second time.

Complete the list and IDR updates, including freeing an empty list head,
before dropping the mutex. Keep the blocking notifier outside the critical
section and retain only the detached request across the callback.

## Which versions are affected by CVE-2026-92506?


## How do I fix CVE-2026-92506?

Apply the vendor's patch.

## Is CVE-2026-92506 being exploited?

There is no known exploitation of CVE-2026-92506 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92506 and fix it if it is affected.

What it is: CVE-2026-92506 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92506 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92506/ (Markdown: https://insights.sbomify.com/CVE-2026-92506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92506
- OSV: https://osv.dev/vulnerability/CVE-2026-92506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92506/
Summaries are generated and may contain mistakes; the official description above is the record.