# CVE-2026-80833: crypto: sun8i-ss - Remove crypto_rng interface

> A use-after-free vulnerability in the sun8i-ss crypto driver allows local attackers to execute code or cause a denial of service.

- **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:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99573, BELL-CVE-2026-80833, DEBIAN-CVE-2026-80833, GHSA-qw2f-jr36-6mwm, UBUNTU-CVE-2026-80833

## What is CVE-2026-80833?

CVE-2026-80833 is an use after free vulnerability in Linux, published on 4 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:

crypto: sun8i-ss - Remove crypto_rng interface

Since the crypto_rng interface for hardware PRNGs is unused and is
redundant with hwrng and the actual Linux RNG, it's being phased out.
Most drivers for it were already removed.  Go ahead and remove the
sun8i-ss support which is one of the only remaining ones.

As usual for crypto_rng, this driver was also buggy: its ->generate()
function had a use-after-free vulnerability due to using
wait_for_completion_interruptible_timeout() without handling shutting
down the DMA operation if a signal is sent.  Also, it had a buffer
overread bug in the line 'memcpy(ctx->seed, d + dlen, ctx->slen);'.
There's no point in fixing these bugs separately only to remove the code
anyway, so this commit is marked with Fixes and Cc stable.

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


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

Apply the vendor's patch.

## Is CVE-2026-80833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80833 is an use after free vulnerability in Linux, published on 4 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-80833 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-80833/ (Markdown: https://insights.sbomify.com/CVE-2026-80833/index.md)
```

## Sources

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

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