CVE-2026-80565

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

crypto: qce - fix error path in devm_qce_register_algs

If ops->register_algs() fails, the error path repeatedly calls the same ops->unregister_algs() from the failed registration. Use the loop index to unregister the previously registered algorithms instead.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (8)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fef187c6194d67395182d58169dd14ba631f1b41
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/de52c713d21806b93b00a6074056b57aec4f8919
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dbca8b798caf47fb2799a26dd09c9ad66305883d
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c7dc487aade12c692add3221673c9bdf32dc24f5
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a134e4b8102c077286818ee112b9f925db613d4c
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c75402286409f5e1a75e4a445555c84066f89db
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e88b4fda48282f3fd504b4d4f5d2d4f996b76ce
generic

crypto: qce - fix error path in devm_qce_register_algs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ece8e16c085e8cd60ecbdb641269aaa53d31da4

Vendor Advisories for CVE-2026-80565(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 02:49 UTCEG score recompute
  2. 2026-08-30 02:49 UTCGHSA enrichment
  3. 2026-08-30 02:48 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 15:30 UTCGHSA enrichment
  6. 2026-08-29 04:13 UTCEG score recompute
  7. 2026-08-29 04:12 UTCGHSA enrichment
  8. 2026-08-28 21:42 UTCEPSS rescore
  9. 2026-08-28 16:51 UTCGHSA enrichment
  10. 2026-08-28 05:32 UTCGHSA enrichment
  11. 2026-08-27 18:04 UTCEG score recompute
  12. 2026-08-27 18:04 UTCGHSA enrichment
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-27 06:18 UTCEG score recompute 7.80
  15. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  16. 2026-08-26 15:43 UTCNVD update
  17. 2026-08-26 14:42 UTCEG score recompute
  18. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80565?
CVE-2026-80565 is a high vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: qce - fix error path in devmqceregister_algs If ops->register_algs() fails, the error path repeatedly calls the same ops->unregister_algs() from the failed registration. Use the loop index to unregister the previously…
When was CVE-2026-80565 disclosed?
CVE-2026-80565 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80565 actively exploited?
CVE-2026-80565 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80565?
CVE-2026-80565 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80565?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80565, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80565

Explore →

Is Your Infrastructure Affected by CVE-2026-80565?

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