GHSA-P9VR-23CC-FH67
Vulnerability from github – Published: 2026-09-04 18:31 – Updated: 2026-09-04 18:31In 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": [],
"aliases": [
"CVE-2026-80835"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-04T16:18:11Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - Remove crypto_rng interface\n\nqcom-rng.c exposes the same hardware through two completely separate\ninterfaces, crypto_rng and hwrng. However, the implementation of this\nis buggy because it permits generation operations from these interfaces\nto run concurrently with each other, accessing the same registers. That\nis, qcom_rng_generate() synchronizes with itself but not with\nqcom_hwrng_read(). This results in potential repetition of output from\nthe RNG, output of non-random values, etc.\n\nFortunately, there\u0027s actually no point in hardware RNG drivers\nimplementing the crypto_rng interface. It\u0027s not actually used by\nanything besides the \"rng\" algorithm type of AF_ALG, which in turn is\nnot actually used in practice. Other crypto_rng hardware drivers are\nlikewise being phased out, leaving just the hwrng support.\n\nThus, remove it to simplify the code and avoid conflict (and confusion)\nwith the hwrng interface which is the one that actually matters.",
"id": "GHSA-p9vr-23cc-fh67",
"modified": "2026-09-04T18:31:28Z",
"published": "2026-09-04T18:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80835"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.