CVE-2026-80835crypto: qcom-rng - Remove crypto_rng interface
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 45 days later
· 45 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f29cd5bb64c258f29b4c49452532481f50eb43ca – < bb474dcd9d0224264a27a60891f00872b879835f
- affected f29cd5bb64c258f29b4c49452532481f50eb43ca – < 14d9ee8286460a7b82f3b8610b5c7ebf4550b06b
- affected f29cd5bb64c258f29b4c49452532481f50eb43ca – < 843e2bdaf8deb8bc341203094dfe582e38ea4af2
- affected f29cd5bb64c258f29b4c49452532481f50eb43ca – < 669d940351eda316b82e24986e2e0e057653ce7d
- affected f29cd5bb64c258f29b4c49452532481f50eb43ca – < 2ecdf5c9910e20f73639bc322f0518a3439d17c0
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.108 – ≤ 6.12.*
- unaffected 6.18.49 – ≤ 6.18.*
- unaffected 7.1.13 – ≤ 7.1.*
- unaffected 7.2.3 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f (opens in a new tab)
- https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b (opens in a new tab)
- https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2 (opens in a new tab)
- https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d (opens in a new tab)
- https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71285 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80835)Record last updated .