# CVE-2026-93163: hwrng: core - fix rng list on registration error

> A use-after-free vulnerability in the Linux kernel hwrng core allows local attackers to potentially execute code or escalate privileges due to improper cleanup on registration failure.

- **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:** 21 Oct 2026
- **Also known as:** AZL-102882, BELL-CVE-2026-93163, DEBIAN-CVE-2026-93163, GHSA-22cg-3qr6-xx65, UBUNTU-CVE-2026-93163

## What is CVE-2026-93163?

CVE-2026-93163 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:

hwrng: core - fix rng list on registration error

hwrng_register(rng) does the following:

1. Checks if rng has name and read methods set
2. Checks if the name already exists
3. Adds rng to global rng_list
4. May try to set rng to current_rng

If step 4 fails, it returns an error. However, it does not remove the
rng from rng_list, causing a dangling reference which can result in
use-after-free if the caller frees rng, since registration failed.

Add a list_del_init() cleanup step.

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


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

Apply the vendor's patch.

## Is CVE-2026-93163 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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