CVE-2026-68300

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.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:

sctp: auth: verify auth requirement when auth_chunk is NULL

sctp_auth_chunk_verify() returns true unconditionally when chunk->auth_chunk is NULL, silently skipping authentication. This is incorrect when:

  • skb_clone() failed in the BH receive path, leaving auth_chunk
NULL. In sctp_endpoint_bh_rcv() asoc is NULL for new connections, so the early sctp_auth_recv_cid() check cannot catch this.
  • No AUTH chunk precedes COOKIE-ECHO, so skb_clone() is never
called and auth_chunk remains NULL.

Fix by checking sctp_auth_recv_cid() when auth_chunk is NULL: if authentication is required, return false to drop the chunk; otherwise continue normally.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

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

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e04823c120b376ef7dab14b60ebf6823aa16c14
generic

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83f5031f2a6a49d696eb4cc0898345d12f9c6451
generic

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6caf0e8590c0bf05a76b0d387726adf3a6f3725c
generic

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28c5fdce9dd955d2baf5e28987819b6d7cfaf646
generic

sctp: auth: verify auth requirement when auth_chunk is NULL - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18957373920caf5cdaf5cf32e5d1d7a99ca7700a

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

Frequently asked(5)

What is CVE-2026-68300?
CVE-2026-68300 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: auth: verify auth requirement when auth_chunk is NULL sctpauthchunk_verify() returns true unconditionally when chunk->auth_chunk is NULL, silently skipping authentication. This is incorrect when: 1. skbclone() failed in the…
When was CVE-2026-68300 disclosed?
CVE-2026-68300 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-68300 actively exploited?
CVE-2026-68300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68300?
CVE-2026-68300 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68300, 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-68300

Explore →

Is Your Infrastructure Affected by CVE-2026-68300?

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

Start Free Scan →Browse All CVEs