What’s Vulnerable › Vulnerabilities
CVE-2026-80835: crypto: qcom-rng - Remove crypto_rng interface
- Severity: unknown
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-04 · updated 2026-10-19
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.
Affected products
- Linux kernel: 6.7 — fixed in 7.3
How to fix
Upgrade to a fixed version: Linux kernel 7.3. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b
- https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0
- https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d
- https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2
- https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f
Get alerted when CVE-2026-80835 or the next vulnerability affects your stack