CVE-2026-80922 crypto: qcom-rng - Allow zero as a random number
Not scored
Published
Updated
Check this codebase for CVE-2026-80922 and fix it if it is affected.
What it is: CVE-2026-80922 is a vulnerability in Linux, published on 9 Sep 2026.
Exploitation: There is no known exploitation of CVE-2026-80922 in the wild and no public exploit code.
Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-80922/ (Markdown: https://insights.sbomify.com/CVE-2026-80922/index.md)
The Qualcomm RNG driver incorrectly rejected zero as a valid random number, making output distinguishable from true randomness.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-80922?
CVE-2026-80922 is a vulnerability in Linux, published on 9 Sep 2026.
Official description
In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - Allow zero as a random number
Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random.
Which versions are affected by CVE-2026-80922?
How do I fix CVE-2026-80922?
Apply the vendor's patch.
Is CVE-2026-80922 being exploited?
There is no known exploitation of CVE-2026-80922 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-80922, DEBIAN-CVE-2026-80922, GHSA-j73x-965w-f4x8, UBUNTU-CVE-2026-80922.