Linux
sctp: add INIT verification after cookie unpacking
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < ca967418a60b33158e859daf202f3858fd1c8afd
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 81892d83cc897331510f35b30d17f8b0dc285966
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 683a012b984fef4bc155e278742fbe01561e102a
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < bca3100f550281c2f2418652338bced3b35af0e6
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 062bcbf8d1f1051fdeb20b94920031b0e2cb95a2
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 414c5447fe6a200613dd46d7fdc8454622076cb1
Fixed in ca967418a60b33158e859daf202f3858fd1c8afd, 81892d83cc897331510f35b30d17f8b0dc285966, 683a012b984fef4bc155e278742fbe01561e102a, bca3100f550281c2f2418652338bced3b35af0e6, 062bcbf8d1f1051fdeb20b94920031b0e2cb95a2, 414c5447fe6a200613dd46d7fdc8454622076cb1
- 2.6.12
Fixed in 0, 6.1.191, 6.6.160, 6.12.114, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to ca967418a60b33158e859daf202f3858fd1c8afd or 81892d83cc897331510f35b30d17f8b0dc285966 or 683a012b984fef4bc155e278742fbe01561e102a or bca3100f550281c2f2418652338bced3b35af0e6 or 062bcbf8d1f1051fdeb20b94920031b0e2cb95a2 or 414c5447fe6a200613dd46d7fdc8454622076cb1 or later.
Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.