CVE-2026-80922

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 9, 2026

Last Modified

September 9, 2026

References (5)

Vendor Advisories for CVE-2026-80922(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (172 versions)
  • every version up to 7.1.13-1: fixed in 7.1.13-1
—

Data Freshness Timeline

(refreshed 12× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 49 are merged into the row they repeat.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 21:56 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  5. 2026-10-11 19:21 UTCEG score recompute
  6. 2026-10-11 16:37 UTCEG score recompute
  7. 2026-10-11 13:55 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-08 23:57 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-05 19:25 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-02 22:40 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  19. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-30 02:02 UTCEG score recompute
  23. 2026-09-30 02:01 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 22 more
  1. 2026-09-26 21:19 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  2. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-24 00:41 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  6. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-21 04:02 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  10. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-18 07:24 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  13. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-09-15 10:46 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  16. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-12 14:06 UTCEG score recompute
  18. 2026-09-12 14:06 UTCGHSA enrichmentGHSA-j73x-965w-f4x8
  19. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-09 17:27 UTCNVD update
  21. 2026-09-09 16:29 UTCEG score recompute
  22. 2026-09-09 16:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80922?
CVE-2026-80922 is a vulnerability whose severity is not yet rated; its CVE record was published on September 9, 2026. 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.
When was the CVE record for CVE-2026-80922 published?
The CVE record for CVE-2026-80922 was published on September 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-80922 actively exploited?
CVE-2026-80922 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80922?
A fix for CVE-2026-80922 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80922 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80922

Explore →

Is Your Infrastructure Affected by CVE-2026-80922?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs