CVE-2026-68376

sctp: fix auth_hmacs array size in struct sctp_cookie

HIGH
8.1
CVSS Score
Published: August 10, 2026 at 12:03 PM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1f485649f52929d9937b346a920a522a7363e2022.6.24
Vendor states this is fixed in 0528485f27016a42804abe01aa61b39d85fa803e (fixed)
Vendor states this is fixed in 0b4414e43e0861d67276031cc21401d7e87de3da (fixed)
Vendor states this is fixed in 317731d01b03c529809df36d3a7d149677a8729d (fixed)
Vendor states this is fixed in 3aa40c3bccac2312ea7cf97f329190637f972b5d (fixed)
Vendor states this is fixed in a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db (fixed)
Vendor states this is fixed in d0a59ba58578e2b330fff80a44fe519f3ba7d8c7 (fixed)
Vendor states this is fixed in e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 (fixed)
Vendor states this is fixed in ee5e65964f456adfe14d526fba0bd055de98ecf3 (fixed)
Vendor states this is fixed in 2.6.24 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card