# CVE-2026-80835: crypto: qcom-rng - Remove crypto_rng interface

> A race condition in the Qualcomm RNG kernel driver allows concurrent access to hardware registers, potentially causing weak or predictable random number generation.

- **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:** BELL-CVE-2026-80835, DEBIAN-CVE-2026-80835, GHSA-p9vr-23cc-fh67, UBUNTU-CVE-2026-80835

## What is CVE-2026-80835?

CVE-2026-80835 is a 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: qcom-rng - Remove crypto_rng interface

qcom-rng.c exposes the same hardware through two completely separate
interfaces, crypto_rng and hwrng.  However, the implementation of this
is buggy because it permits generation operations from these interfaces
to run concurrently with each other, accessing the same registers.  That
is, qcom_rng_generate() synchronizes with itself but not with
qcom_hwrng_read().  This results in potential repetition of output from
the RNG, output of non-random values, etc.

Fortunately, there's actually no point in hardware RNG drivers
implementing the crypto_rng interface.  It's not actually used by
anything besides the "rng" algorithm type of AF_ALG, which in turn is
not actually used in practice.  Other crypto_rng hardware drivers are
likewise being phased out, leaving just the hwrng support.

Thus, remove it to simplify the code and avoid conflict (and confusion)
with the hwrng interface which is the one that actually matters.

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


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

Apply the vendor's patch.

## Is CVE-2026-80835 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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