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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
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.
Sources
Also known as BELL-CVE-2026-80835, DEBIAN-CVE-2026-80835, GHSA-p9vr-23cc-fh67, UBUNTU-CVE-2026-80835.