Strix
63.3K

CVE-2026-80835

Unknown

Last modified

CVE-2026-80835 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f29cd5bb64c258f29b4c49452532481f50eb43ca, < bb474dcd9d0224264a27a60891f00872b879835f; >= f29cd5bb64c258f29b4c49452532481f50eb43ca, < 14d9ee8286460a7b82f3b8610b5c7ebf4550b06b; >= f29cd5bb64c258f29b4c49452532481f50eb43ca, < 843e2bdaf8deb8bc341203094dfe582e38ea4af2; >= f29cd5bb64c258f29b4c49452532481f50eb43ca, < 669d940351eda316b82e24986e2e0e057653ce7d; >= f29cd5bb64c258f29b4c49452532481f50eb43ca, < 2ecdf5c9910e20f73639bc322f0518a3439d17c0
LinuxLinux6.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80835?
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.
How severe is CVE-2026-80835?
Severity scoring for CVE-2026-80835 is pending analysis.
How do I fix CVE-2026-80835?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80835?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST