# CVE-2026-92490: firmware: arm_scmi: Unrequest devices if driver registration fails

> A use-after-free in the Linux kernel SCMI driver allows local attackers to cause a crash or potentially execute code if driver registration fails.

- **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-102597, BELL-CVE-2026-92490, DEBIAN-CVE-2026-92490, GHSA-xhxg-9qcq-hmmp, UBUNTU-CVE-2026-92490

## What is CVE-2026-92490?

CVE-2026-92490 is an use after free 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: Unrequest devices if driver registration fails

scmi_driver_register() requests protocol devices before registering the
driver. If driver_register() fails, those requests remain in the global
IDR and retain pointers to the module's ID table. Once the failed module
load releases that storage, later request matching or SCMI device creation
can dereference the stale pointers.

Unrequest the complete protocol table before returning the registration
failure. At this point table registration succeeded, so every entry is
owned by the current registration attempt.

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


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

Apply the vendor's patch.

## Is CVE-2026-92490 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92490 is an use after free 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-92490 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-92490/ (Markdown: https://insights.sbomify.com/CVE-2026-92490/index.md)
```

## Sources

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

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