CVE-2026-80522

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: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()

Perform rctx->cryptlen calculation in tegra_gcm_do_one_req() the same way it is done in tegra_ccm_crypt_init(). The current formulae may lead to a crash if a caller does not call tegra_gcm_setauthsize() and so ctx->authsize remains zero. Then a decrypt operation with incorrect rctx->cryptlen will lead to a write beyound rctx->dst_sg buffer.

As a follow-up cleanup delete struct tegra_aead_ctx->authsize field since it appears to be completely unused. Also simplify tegra_ccm_setauthsize() and tegra_gcm_setauthsize() functions respectively.

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
3%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (4)

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

crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req() - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req() - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99a18e1d979e0fad3aaf9c65ae6696897c1d9869
generic

crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/360f2974fcea49c61f6d6f81554741a9eeee7168

Vendor Advisories for CVE-2026-80522(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 15× in last 7d / 15× 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 01:22 UTCEPSS rescore
  2. 2026-08-29 19:52 UTCGHSA enrichment
  3. 2026-08-29 07:38 UTCEG score recompute
  4. 2026-08-29 07:38 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 19:23 UTCGHSA enrichment
  7. 2026-08-28 06:54 UTCGHSA enrichment
  8. 2026-08-27 18:39 UTCEG score recompute
  9. 2026-08-27 18:38 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 06:21 UTCEG score recompute▲ 7.80
  12. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  13. 2026-08-26 15:43 UTCNVD update
  14. 2026-08-26 14:43 UTCEG score recompute
  15. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80522?
CVE-2026-80522 is a high vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - fix rctx->cryptlen calculation in tegragcmdoonereq() Perform rctx->cryptlen calculation in tegragcmdoonereq() the same way it is done in tegraccmcrypt_init(). The current formulae may lead to a crash if a caller…
When was CVE-2026-80522 disclosed?
CVE-2026-80522 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-80522 actively exploited?
CVE-2026-80522 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80522?
CVE-2026-80522 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80522, 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-80522

Explore →

Is Your Infrastructure Affected by CVE-2026-80522?

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

Start Free Scan →Browse All CVEs