# CVE-2026-92491: firmware: arm_scmi: Roll back partial protocol table registration

> A use-after-free vulnerability in the Linux kernel SCMI driver allows local attackers to execute arbitrary code or escalate privileges via a failed module load.

- **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:** BELL-CVE-2026-92491, DEBIAN-CVE-2026-92491, GHSA-hcj6-qcrw-498h, UBUNTU-CVE-2026-92491

## What is CVE-2026-92491?

CVE-2026-92491 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: Roll back partial protocol table registration

scmi_protocol_table_register() can leave earlier requests registered when
a later entry in the same ID table fails. Each request retains a pointer
to the driver's ID table, so a failed module load can leave a dangling
pointer after the module storage is released.

Unrequest only the successfully registered prefix, in reverse order,
before returning the failure. Leave the failed entry and the remaining
entries untouched because matching requests can be owned by another
driver.

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


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

Apply the vendor's patch.

## Is CVE-2026-92491 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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