crypto: qcom-rng - Allow zero as a random number (CVE-2026-80922) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80922

crypto: qcom-rng - Allow zero as a random number

Answer in brief

CVE-2026-80922 records a Unknown severity vulnerability in crypto: qcom-rng - Allow zero as a random number. 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.

Published Sep 9, 2026Updated Sep 9, 2026Source checked Sep 9, 2026First seen by HOL Sep 9, 2026Material review Sep 9, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=f29cd5bb64c258f29b4c49452532481f50eb43ca <813e6718a199befc4f26f54bdd899fbfa11515e5 \|\| >=f29cd5bb64c258f29b4c49452532481f50eb43ca <4c0018320942003bfedd0a1c4cce3f036d363a7f \|\| >=f29cd5bb64c258f29b4c49452532481f50eb43ca <143c74034a1c47b0a1a64e7ca7153e7739bd1244 \|\| >=f29cd5bb64c258f29b4c49452532481f50eb43ca <3c7101cfc52e378bcb0a46962145e39c9051dd5d \|\| >=f29cd5bb64c258f29b4c49452532481f50eb43ca <4ef04bdc0c9f98836d1638be516f6bf1bad55f69	813e6718a199befc4f26f54bdd899fbfa11515e5, 4c0018320942003bfedd0a1c4cce3f036d363a7f, 143c74034a1c47b0a1a64e7ca7153e7739bd1244, 3c7101cfc52e378bcb0a46962145e39c9051dd5d, 4ef04bdc0c9f98836d1638be516f6bf1bad55f69
Linux/Linuxgeneric	6.7	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 813e6718a199befc4f26f54bdd899fbfa11515e5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 9, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.