Bug 2492771 (CVE-2026-53246) - CVE-2026-53246 kernel: sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing
Summary: CVE-2026-53246 kernel: sctp: validate cached peer INIT chunk length in COOKIE...
Keywords:
Status: NEW
Alias: CVE-2026-53246
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-25 10:04 UTC by OSIDB Bzimport
Modified: 2026-09-15 06:14 UTC (History)
2 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:66324 0 None None None 2026-09-10 05:18:39 UTC
Red Hat Product Errata RHSA-2026:66325 0 None None None 2026-09-10 05:39:58 UTC
Red Hat Product Errata RHSA-2026:67150 0 None None None 2026-09-14 13:36:08 UTC
Red Hat Product Errata RHSA-2026:67471 0 None None None 2026-09-15 06:14:27 UTC

Description OSIDB Bzimport 2026-06-25 10:04:52 UTC
In the Linux kernel, the following vulnerability has been resolved:

sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing

When a listening SCTP server processes a COOKIE_ECHO chunk, the cached
peer INIT chunk embedded after the cookie is parsed and its parameters
are later walked by sctp_process_init() using sctp_walk_params().

However, the chunk header length of this cached INIT chunk was not
validated against the remaining buffer in the COOKIE_ECHO payload. If
the length field is inflated, the parameter walk can run beyond the
actual received data, leading to out-of-bounds reads and potential
memory corruption during later parameter handling (e.g. STATE_COOKIE
processing and kmemdup() copies).

Add a bounds check in sctp_unpack_cookie() to ensure the cached INIT
chunk length does not exceed the available data in the COOKIE_ECHO
buffer before it is used.

Comment 4 errata-xmlrpc 2026-09-10 05:18:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:66324 https://access.redhat.com/errata/RHSA-2026:66324

Comment 5 errata-xmlrpc 2026-09-10 05:39:57 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:66325 https://access.redhat.com/errata/RHSA-2026:66325

Comment 6 Jon Orris 2026-09-14 13:36:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:67150 https://access.redhat.com/errata/RHSA-2026:67150

Comment 7 Jon Orris 2026-09-15 06:14:27 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:67471 https://access.redhat.com/errata/RHSA-2026:67471


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