CVE-2026-68376

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

sctp: fix auth_hmacs array size in struct sctp_cookie

The auth_hmacs array in struct sctp_cookie is supposed to store a complete SCTP_AUTH_HMAC_ALGO parameter, which consists of a struct sctp_paramhdr followed by N HMAC identifiers.

However, the array size was calculated using an extra 2 bytes instead of sizeof(struct sctp_paramhdr), which is 4 bytes. When four HMAC identifiers are configured, the HMAC-ALGO parameter stored in the endpoint is larger than the auth_hmacs buffer in the cookie.

As a result, sctp_association_init() copies beyond the end of auth_hmacs when initializing the association, corrupting the adjacent auth_chunks field. This can lead to an invalid HMAC identifier being accepted and later cause an out-of-bounds read in sctp_auth_get_hmac().

Fix the array size calculation by including the full SCTP parameter header size.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
41
EG Risk 41/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
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
Patch available.
generic

sctp: fix auth_hmacs array size in struct sctp_cookie - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix auth_hmacs array size in struct sctp_cookie - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix auth_hmacs array size in struct sctp_cookie - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix auth_hmacs array size in struct sctp_cookie - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3aa40c3bccac2312ea7cf97f329190637f972b5d
generic

sctp: fix auth_hmacs array size in struct sctp_cookie - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b4414e43e0861d67276031cc21401d7e87de3da

Vendor Advisories for CVE-2026-68376(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.el8_102026-09-10redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 24× in last 7d / 129× 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.

Showing the most recent 100 of 256 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:50 UTCVendor advisory
  3. 2026-10-04 22:50 UTCGHSA enrichment
  4. 2026-10-04 05:21 UTCEG score recompute
  5. 2026-10-04 05:21 UTCVendor advisory
  6. 2026-10-04 05:21 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 00:53 UTCEG score recompute
  9. 2026-10-03 00:53 UTCVendor advisory
  10. 2026-10-03 00:53 UTCGHSA enrichment
  11. 2026-10-02 17:56 UTCEPSS rescore
  12. 2026-10-02 09:20 UTCEG score recompute
  13. 2026-10-02 09:20 UTCVendor advisory
  14. 2026-10-02 09:20 UTCGHSA enrichment
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-10-01 10:53 UTCVendor advisory
  17. 2026-10-01 10:53 UTCGHSA enrichment
  18. 2026-09-30 22:37 UTCEG score recompute
  19. 2026-09-30 22:37 UTCVendor advisory
  20. 2026-09-30 22:37 UTCGHSA enrichment
  21. 2026-09-30 15:03 UTCEPSS rescore
  22. 2026-09-29 05:23 UTCEG score recompute
  23. 2026-09-29 05:23 UTCVendor advisory
  24. 2026-09-29 05:23 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-28 02:24 UTCEG score recompute
  2. 2026-09-28 02:24 UTCVendor advisory
  3. 2026-09-28 02:24 UTCGHSA enrichment
  4. 2026-09-27 13:48 UTCEPSS rescore
  5. 2026-09-27 13:00 UTCEG score recompute
  6. 2026-09-27 13:00 UTCVendor advisory
  7. 2026-09-27 12:59 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 04:03 UTCEG score recompute
  10. 2026-09-25 04:03 UTCVendor advisory
  11. 2026-09-25 04:03 UTCGHSA enrichment
  12. 2026-09-24 11:37 UTCVendor advisory
  13. 2026-09-24 11:37 UTCGHSA enrichment
  14. 2026-09-23 23:36 UTCEG score recompute
  15. 2026-09-23 23:36 UTCVendor advisory
  16. 2026-09-23 23:36 UTCGHSA enrichment
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 10:53 UTCVendor advisory
  19. 2026-09-23 10:53 UTCGHSA enrichment
  20. 2026-09-22 22:59 UTCEG score recompute
  21. 2026-09-22 22:59 UTCVendor advisory
  22. 2026-09-22 22:59 UTCGHSA enrichment
  23. 2026-09-22 11:03 UTCVendor advisory
  24. 2026-09-22 11:02 UTCGHSA enrichment
  25. 2026-09-21 23:08 UTCEG score recompute
  26. 2026-09-21 23:08 UTCVendor advisory
  27. 2026-09-21 23:08 UTCGHSA enrichment
  28. 2026-09-21 21:09 UTCEPSS rescore
  29. 2026-09-21 11:12 UTCVendor advisory
  30. 2026-09-21 11:12 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEG score recompute
  32. 2026-09-20 20:16 UTCVendor advisory
  33. 2026-09-20 20:16 UTCGHSA enrichment
  34. 2026-09-20 20:16 UTCEPSS rescore
  35. 2026-09-20 03:00 UTCEG score recompute
  36. 2026-09-20 03:00 UTCVendor advisory
  37. 2026-09-20 02:59 UTCGHSA enrichment
  38. 2026-09-19 14:46 UTCVendor advisory
  39. 2026-09-19 14:46 UTCGHSA enrichment
  40. 2026-09-19 02:43 UTCEG score recompute
  41. 2026-09-19 02:43 UTCVendor advisory
  42. 2026-09-19 02:43 UTCGHSA enrichment
  43. 2026-09-18 19:28 UTCEPSS rescore
  44. 2026-09-18 14:44 UTCVendor advisory
  45. 2026-09-18 14:44 UTCGHSA enrichment
  46. 2026-09-18 02:50 UTCEG score recompute
  47. 2026-09-18 02:50 UTCVendor advisory
  48. 2026-09-18 02:50 UTCGHSA enrichment
  49. 2026-09-17 14:56 UTCVendor advisory
  50. 2026-09-17 14:56 UTCGHSA enrichment
  51. 2026-09-17 00:46 UTCEG score recompute
  52. 2026-09-17 00:46 UTCVendor advisory
  53. 2026-09-17 00:46 UTCGHSA enrichment
  54. 2026-09-16 14:08 UTCEPSS rescore
  55. 2026-09-16 05:15 UTCEPSS rescore
  56. 2026-09-16 02:33 UTCVendor advisory
  57. 2026-09-16 02:33 UTCGHSA enrichment
  58. 2026-09-15 13:53 UTCEG score recompute
  59. 2026-09-15 13:53 UTCVendor advisory
  60. 2026-09-15 13:53 UTCGHSA enrichment
  61. 2026-09-15 00:30 UTCVendor advisory
  62. 2026-09-15 00:30 UTCGHSA enrichment
  63. 2026-09-14 05:37 UTCVendor advisory
  64. 2026-09-14 05:37 UTCGHSA enrichment
  65. 2026-09-13 17:43 UTCEG score recompute
  66. 2026-09-13 17:43 UTCVendor advisory
  67. 2026-09-13 17:43 UTCGHSA enrichment
  68. 2026-09-13 05:49 UTCVendor advisory
  69. 2026-09-13 05:49 UTCGHSA enrichment
  70. 2026-09-12 17:55 UTCEG score recompute
  71. 2026-09-12 17:55 UTCVendor advisory
  72. 2026-09-12 17:55 UTCGHSA enrichment
  73. 2026-09-12 06:01 UTCVendor advisory
  74. 2026-09-12 06:01 UTCGHSA enrichment
  75. 2026-09-11 18:07 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68376?
CVE-2026-68376 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: fix authhmacs array size in struct sctpcookie The authhmacs array in struct sctpcookie is supposed to store a complete SCTPAUTHHMACALGO parameter, which consists of a struct sctpparamhdr followed by N HMAC identifiers.…
When was CVE-2026-68376 disclosed?
CVE-2026-68376 was first published 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-68376 actively exploited?
CVE-2026-68376 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68376?
CVE-2026-68376 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68376?
A fix for CVE-2026-68376 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68376 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-68376

Explore →

Is Your Infrastructure Affected by CVE-2026-68376?

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

Book a Demo →Browse All CVEs