CVE-2026-90069

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

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

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

crypto: acomp - allocate async request context when cloning

ACOMP_REQUEST_ON_STACK() reserves only enough storage for the synchronous fallback. When an async implementation is selected, callers clone that stack request before retrying, but acomp_request_clone() currently copies only the stack-sized object. The clone therefore has no storage for the async provider request context, and providers such as QAT write past the allocation through acomp_request_ctx(). KASAN does report a slab OOB write.

Allocate a zeroed clone large enough for the runtime acomp request size, copy only the bytes present in the source object, and preserve the existing fallback-on-allocation-failure behavior. Use the runtime reqsize because an implementation may adjust it during tfm initialization.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

crypto: acomp - allocate async request context when cloning - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: acomp - allocate async request context when cloning - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: acomp - allocate async request context when cloning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/889fa17a0af09ff93a9166abc82ee7a654faa49b

Vendor Advisories for CVE-2026-90069(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 71× 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-10-05 04:23 UTCGHSA enrichment
  2. 2026-10-04 17:14 UTCGHSA enrichment
  3. 2026-10-04 05:58 UTCGHSA enrichment
  4. 2026-10-03 18:50 UTCEG score recompute
  5. 2026-10-03 18:50 UTCGHSA enrichment
  6. 2026-10-03 06:49 UTCGHSA enrichment
  7. 2026-10-02 19:40 UTCEG score recompute
  8. 2026-10-02 19:40 UTCGHSA enrichment
  9. 2026-10-02 08:31 UTCGHSA enrichment
  10. 2026-10-01 21:21 UTCEG score recompute
  11. 2026-10-01 21:21 UTCGHSA enrichment
  12. 2026-10-01 19:51 UTCEPSS rescore
  13. 2026-10-01 10:13 UTCGHSA enrichment
  14. 2026-09-30 23:04 UTCEG score recompute
  15. 2026-09-30 23:04 UTCGHSA enrichment
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 11:54 UTCGHSA enrichment
  18. 2026-09-30 00:45 UTCEG score recompute
  19. 2026-09-30 00:45 UTCGHSA enrichment
  20. 2026-09-29 11:43 UTCGHSA enrichment
  21. 2026-09-29 00:31 UTCEG score recompute
  22. 2026-09-29 00:31 UTCGHSA enrichment
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 13:21 UTCGHSA enrichment
Show 46 more
  1. 2026-09-28 02:12 UTCGHSA enrichment
  2. 2026-09-27 15:03 UTCEG score recompute
  3. 2026-09-27 15:03 UTCGHSA enrichment
  4. 2026-09-27 13:49 UTCEPSS rescore
  5. 2026-09-27 03:54 UTCGHSA enrichment
  6. 2026-09-26 16:45 UTCEG score recompute
  7. 2026-09-26 16:44 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 05:32 UTCEG score recompute
  10. 2026-09-26 05:32 UTCGHSA enrichment
  11. 2026-09-25 18:22 UTCGHSA enrichment
  12. 2026-09-25 06:40 UTCGHSA enrichment
  13. 2026-09-24 19:31 UTCEG score recompute
  14. 2026-09-24 19:31 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 08:22 UTCGHSA enrichment
  17. 2026-09-23 21:13 UTCEG score recompute
  18. 2026-09-23 21:13 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 10:05 UTCGHSA enrichment
  21. 2026-09-22 22:56 UTCEG score recompute
  22. 2026-09-22 22:55 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 11:44 UTCGHSA enrichment
  25. 2026-09-22 00:35 UTCEG score recompute
  26. 2026-09-22 00:35 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 13:26 UTCGHSA enrichment
  29. 2026-09-21 02:17 UTCEG score recompute
  30. 2026-09-21 02:17 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 15:07 UTCGHSA enrichment
  33. 2026-09-20 03:59 UTCGHSA enrichment
  34. 2026-09-19 16:49 UTCEG score recompute
  35. 2026-09-19 16:49 UTCGHSA enrichment
  36. 2026-09-19 05:40 UTCEG score recompute
  37. 2026-09-19 05:40 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 18:31 UTCEG score recompute
  40. 2026-09-18 18:31 UTCGHSA enrichment
  41. 2026-09-18 18:06 UTCEG score recompute▲ 7.80
  42. 2026-09-18 18:06 UTCGHSA enrichment
  43. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  44. 2026-09-17 17:23 UTCNVD update
  45. 2026-09-17 16:52 UTCEG score recompute
  46. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90069?
CVE-2026-90069 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: acomp - allocate async request context when cloning ACOMPREQUESTON_STACK() reserves only enough storage for the synchronous fallback. When an async implementation is selected, callers clone that stack request before…
When was CVE-2026-90069 disclosed?
CVE-2026-90069 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90069 actively exploited?
CVE-2026-90069 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90069?
CVE-2026-90069 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90069?
No fix for CVE-2026-90069 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90069 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-90069

Explore →

Is Your Infrastructure Affected by CVE-2026-90069?

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

Book a Demo →Browse All CVEs