Skip to main content

Linux Kernel EUVDEUVD-2026-55562

| CVE-2026-68376 HIGH
2026-08-10 Linux GHSA-55hr-9mvf-6m8f
8.1
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.1 HIGH

AC:H reflects the mandatory non-default SCTP auth with four HMACs; AV:N is valid as SCTP can be network-routable; PR:N as no authentication is needed to send SCTP INIT packets.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
7.0 HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 02:58 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
8.1 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:03 cve.org
HIGH 8.1
CVE Published
Aug 10, 2026 - 12:03 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Stack-based buffer overflow in the Linux kernel's SCTP subsystem corrupts adjacent kernel memory when SCTP authentication is configured with four HMAC identifiers, enabling a remote unauthenticated attacker to achieve high-impact memory corruption via a crafted SCTP packet exchange. Affected kernels span from 2.6.24 through current stable branches, with patches backported to 6.6.148, 6.12.101, 6.18.42, 7.1.6, and 7.2-rc4. No public exploit code or CISA KEV listing has been identified; the EPSS score of 0.17% reflects the high exploitation complexity imposed by the required SCTP authentication configuration.

Technical ContextAI

SCTP (Stream Control Transmission Protocol) authentication is defined in RFC 4895 and implemented in the Linux kernel's net/sctp subsystem. The vulnerability originates in an off-by-two sizing error in struct sctp_cookie: the auth_hmacs array was dimensioned using 2 extra bytes rather than the full sizeof(struct sctp_paramhdr) which is 4 bytes, producing a 2-byte undersized buffer. When a peer endpoint advertises exactly four HMAC identifiers, the HMAC-ALGO parameter stored in the endpoint exceeds the auth_hmacs buffer capacity. During sctp_association_init(), the kernel copies this oversized parameter beyond the end of auth_hmacs, silently corrupting the adjacent auth_chunks field in the same cookie structure. The corrupted auth_chunks value can cause an invalid HMAC identifier to pass validation, which subsequently triggers an out-of-bounds read in sctp_auth_get_hmac(). Although the NVD does not assign a CWE, this maps directly to CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) with a secondary CWE-125 (Out-of-bounds Read) in the follow-on path. The bug was introduced with commit 1f485649f52929d9937b346a920a522a7363e202, present since Linux 2.6.24 when SCTP authentication support was added.

RemediationAI

Upgrade to a patched kernel release: 6.6.148, 6.12.101, 6.18.42, 7.1.6, or 7.2-rc4, depending on the stable branch in use. Stable tree commits are available at https://git.kernel.org/stable/c/0b4414e43e0861d67276031cc21401d7e87de3da, https://git.kernel.org/stable/c/d0a59ba58578e2b330fff80a44fe519f3ba7d8c7, https://git.kernel.org/stable/c/a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db, https://git.kernel.org/stable/c/3aa40c3bccac2312ea7cf97f329190637f972b5d, and https://git.kernel.org/stable/c/e0b5252a59383b77d1b8dbeda00b7184dd95f4d3. For systems where SCTP is not operationally required, unloading the sctp kernel module (modprobe -r sctp and blacklisting it in /etc/modprobe.d/) eliminates the attack surface entirely with no impact to non-SCTP traffic, though it will break any SCTP-dependent application or socket. On systems that require SCTP but can restrict HMAC configuration, limiting the endpoint to three or fewer HMAC identifiers avoids triggering the undersized buffer, though this is an application-level workaround that depends on implementation details and should not substitute for patching.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-55562 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy