All reports
High

kernel: sctp: validate cookie AUTH state before use

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-74752

Probability of exploitation in the next 30 days: 0.52%

FIRST EPSS · 2026-11-17

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: validate cookie AUTH state before use When cookie authentication is disabled, COOKIE_ECHO restores fixed-size AUTH fields directly from peer-controlled cookie bytes. A forged RANDOM length, HMAC list, or CHUNKS list can then reach association consumers with lengths or identifiers that were never validated against the local backing arrays. A forged RANDOM length can cause out-of-bounds reads during key-vector construction. A forged HMAC identifier also caused a 32-byte write past a zero-length AUTH chunk, providing a primitive for a local privilege escalation chain. Validate the cookie's RANDOM, HMACS, and CHUNKS parameters at the cookie trust boundary before copying them into the association. Reject invalid types, malformed lengths, unsupported HMAC identifiers, HMAC lists without SHA1, and forbidden chunk ids.

A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP). When cookie authentication is disabled, the system improperly validates authentication (AUTH) fields restored directly from peer-controlled cookie bytes. A local attacker could exploit this by forging RANDOM lengths or HMAC identifiers within these cookies. This could lead to out-of-bounds reads and, more critically, a 32-byte write past a zero-length AUTH chunk, providing a primitive for local privilege escalation.