CVE-2026-68320

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
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.3Exploit: 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:

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid

sctp_auth_ep_add_chunkid() uses SCTP_NUM_CHUNK_TYPES (20) as the capacity limit for ep->auth_chunk_list, allowing it to hold up to 20 chunk entries (param_hdr.length up to 24). However, the copy destination asoc->c.auth_chunks in struct sctp_cookie is only SCTP_AUTH_MAX_CHUNKS (16) entries (20 bytes). When more than 16 chunks are added, sctp_association_init() memcpy overflows the destination by up to 4 bytes.

Fix by using SCTP_AUTH_MAX_CHUNKS as the capacity limit, matching the destination capacity.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
37(Track)
EG Risk 37/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
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/886e28e14ab655012779016d251fef53d103aa12
generic

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a365f1e423444c5da7eb689a8661633dad43e48
generic

sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11092d79eb2b7c0068382f72fc2416d1786bb2e0

Vendor Advisories for CVE-2026-68320(2)

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 40× in last 7d / 44× 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-20 16:59 UTCGHSA enrichment
  2. 2026-08-20 05:13 UTCGHSA enrichment
  3. 2026-08-19 17:24 UTCEG score recompute
  4. 2026-08-19 17:24 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 16:54 UTCEG score recompute
  7. 2026-08-19 16:54 UTCGHSA enrichment
  8. 2026-08-19 05:19 UTCGHSA enrichment
  9. 2026-08-18 17:25 UTCEG score recompute
  10. 2026-08-18 17:25 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 05:13 UTCGHSA enrichment
  14. 2026-08-17 17:24 UTCEG score recompute
  15. 2026-08-17 17:23 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:37 UTCEG score recompute
  18. 2026-08-17 05:37 UTCGHSA enrichment
  19. 2026-08-17 05:06 UTCEG score recompute
  20. 2026-08-17 05:06 UTCGHSA enrichment
  21. 2026-08-16 22:21 UTCEG score recompute
  22. 2026-08-16 22:21 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 10:35 UTCEG score recompute
  25. 2026-08-16 10:35 UTCGHSA enrichment
Show 19 more
  1. 2026-08-15 22:49 UTCGHSA enrichment
  2. 2026-08-15 11:03 UTCEG score recompute
  3. 2026-08-15 11:03 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 23:17 UTCGHSA enrichment
  6. 2026-08-14 11:31 UTCEG score recompute
  7. 2026-08-14 11:31 UTCGHSA enrichment
  8. 2026-08-13 23:45 UTCEG score recompute
  9. 2026-08-13 23:45 UTCGHSA enrichment
  10. 2026-08-13 23:04 UTCEG score recompute▲ 7.30
  11. 2026-08-13 23:04 UTCGHSA enrichment
  12. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.3 · severity → HIGH
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 20:24 UTCEG score recompute
  15. 2026-08-13 20:24 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:19 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68320?
CVE-2026-68320 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: fix authchunklist capacity check in sctpauthepaddchunkid sctpauthepaddchunkid() uses SCTPNUMCHUNK_TYPES (20) as the capacity limit for ep->authchunklist, allowing it to hold up to 20 chunk entries (param_hdr.length up to 24).…
When was CVE-2026-68320 disclosed?
CVE-2026-68320 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68320 actively exploited?
CVE-2026-68320 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-68320?
CVE-2026-68320 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-68320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68320, 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-68320

Explore →

Is Your Infrastructure Affected by CVE-2026-68320?

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

Start Free Scan →Browse All CVEs