Bug 2524422 (CVE-2026-74752) - CVE-2026-74752 kernel: sctp: validate cookie AUTH state before use
Summary: CVE-2026-74752 kernel: sctp: validate cookie AUTH state before use
Keywords:
Status: NEW
Alias: CVE-2026-74752
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-26 14:47 UTC by OSIDB Bzimport
Modified: 2026-08-29 22:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-26 14:47:52 UTC
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.

Comment 3 Akiyoshi Kurita 2026-08-29 22:33:25 UTC
A possible mitigation for systems that do not require SCTP may be to prevent the SCTP kernel module from loading:


echo 'install sctp /bin/false' > /etc/modprobe.d/disable-sctp.conf


If the module is already loaded and SCTP is not in use:


modprobe -r sctp


RHEL kernels build SCTP as a module (`CONFIG_IP_SCTP=m`), so disabling the `sctp` module should prevent the vulnerable SCTP code path from being reachable.

This mitigation is only suitable for systems that do not require SCTP.


Note You need to log in before you can comment on or make changes to this bug.