sctp: add INIT verification after cookie unpacking

Overview

In the Linux kernel, the following vulnerability has been resolved:

sctp: add INIT verification after cookie unpacking

In SCTP handshake, the INIT chunk is initially processed by the server and embedded into the cookie carried in INIT-ACK. The client then returns this cookie via COOKIE-ECHO, where the server unpacks it and reconstructs the original INIT chunk.

When cookie authentication is enabled, the cookie contents are protected against tampering, so reusing the unpacked INIT without re-verification is safe.

However, when cookie authentication is disabled, the reconstructed INIT can no longer be trusted. In this case, the INIT must be explicitly validated after unpacking to avoid processing potentially tampered data.

Add sctp_verify_init() checks after cookie unpacking in COOKIE-ECHO processing paths (sctp_sf_do_5_1D_ce() and sctp_sf_do_5_2_4_dupcook()) when cookie_auth_enable is disabled. On failure, the new association is freed and the packet is discarded.

Also tighten cookie validation in sctp_unpack_cookie() by verifying the embedded chunk type is SCTP_CID_INIT before treating it as an INIT chunk.

Finally, update sctp_verify_init() to validate parameter bounds using the actual embedded INIT length instead of chunk->chunk_end, since the INIT stored in COOKIE-ECHO may not span the entire chunk buffer.

Affected

• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 81892d83cc897331510f35b30d17f8b0dc285966
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 683a012b984fef4bc155e278742fbe01561e102a
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bca3100f550281c2f2418652338bced3b35af0e6
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 062bcbf8d1f1051fdeb20b94920031b0e2cb95a2
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 414c5447fe6a200613dd46d7fdc8454622076cb1
• Linux 2.6.12

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.