CVE-2026-80835

crypto: qcom-rng - Remove crypto_rng interface

State
Published
Severity
Not scored
Published
Sep 4, 2026
Updated
Oct 19, 2026
Reserved
Aug 26, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • f29cd5bb64c258f29b4c49452532481f50eb43ca to before bb474dcd9d0224264a27a60891f00872b879835fAffected
  • f29cd5bb64c258f29b4c49452532481f50eb43ca to before 14d9ee8286460a7b82f3b8610b5c7ebf4550b06bAffected
  • f29cd5bb64c258f29b4c49452532481f50eb43ca to before 843e2bdaf8deb8bc341203094dfe582e38ea4af2Affected
  • f29cd5bb64c258f29b4c49452532481f50eb43ca to before 669d940351eda316b82e24986e2e0e057653ce7dAffected
  • f29cd5bb64c258f29b4c49452532481f50eb43ca to before 2ecdf5c9910e20f73639bc322f0518a3439d17c0Affected
LinuxLinux
  • 6.7Affected
  • before 6.7Not affected
  • 6.12.108 through 6.12.*Not affected
  • 6.18.49 through 6.18.*Not affected
  • 7.1.13 through 7.1.*Not affected
  • 7.2.3 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.