Answer in brief
CVE-2026-80835 records a Unknown severity vulnerability in crypto: qcom-rng - Remove crypto_rng interface. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f29cd5bb64c258f29b4c49452532481f50eb43ca <bb474dcd9d0224264a27a60891f00872b879835f || >=f29cd5bb64c258f29b4c49452532481f50eb43ca <14d9ee8286460a7b82f3b8610b5c7ebf4550b06b || >=f29cd5bb64c258f29b4c49452532481f50eb43ca <843e2bdaf8deb8bc341203094dfe582e38ea4af2 || >=f29cd5bb64c258f29b4c49452532481f50eb43ca <669d940351eda316b82e24986e2e0e057653ce7d || >=f29cd5bb64c258f29b4c49452532481f50eb43ca <2ecdf5c9910e20f73639bc322f0518a3439d17c0 | bb474dcd9d0224264a27a60891f00872b879835f, 14d9ee8286460a7b82f3b8610b5c7ebf4550b06b, 843e2bdaf8deb8bc341203094dfe582e38ea4af2, 669d940351eda316b82e24986e2e0e057653ce7d, 2ecdf5c9910e20f73639bc322f0518a3439d17c0 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.