CVE-2026-53224sctp: validate embedded INIT chunk and address list lengths in cookie
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded INIT chunk and address list lengths in cookie sctp_unpack_cookie() only checked that the embedded INIT chunk length did not exceed the remaining cookie payload, but did not ensure that the INIT chunk is large enough to contain a complete INIT header. A malformed COOKIE_ECHO can therefore carry a truncated INIT chunk whose length field is smaller than sizeof(struct sctp_init_chunk). Later, sctp_process_init() accesses INIT parameters unconditionally, which may lead to out-of-bounds reads. In addition, raw_addr_list_len is not fully validated against the remaining cookie payload. When cookie authentication is disabled, an attacker can supply an oversized raw_addr_list_len and cause sctp_raw_to_bind_addrs() to read beyond the end of the cookie. The address parser also lacks sufficient bounds checks for parameter headers and lengths, allowing malformed address parameters to trigger out-of-bounds reads. Fix this by: - requiring the embedded INIT chunk length to be at least sizeof(struct sctp_init_chunk); - validating that the INIT chunk and raw address list together fit within the cookie payload; - verifying sufficient data exists for each address parameter header and payload before parsing it. Note that sctp_verify_init() must be called after sctp_unpack_cookie() and before sctp_process_init() when cookie authentication is disabled. This will be addressed in a separate patch.
- CVSS
- 9.1 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 7560afb8cddafd829e709d7ea09230e45a825557; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 512a9bb77c04ac9927648ea58af617e472be96e6; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 6f4c80a2a7e6d06753b89a578b710a2499a5e62b | CNA record |
linux linux_kernel linux:linux_kernel | from 2.6.12.1 before 6.18.36; from 6.19 before 7.0.13; 2.6.12; 2.6.12; 2.6.12; 2.6.12; 2.6.12; 7.1; and 6 more ranges | NVD |
References
- https://git.kernel.org/stable/c/7560afb8cddafd829e709d7ea09230e45a825557patch
- https://git.kernel.org/stable/c/512a9bb77c04ac9927648ea58af617e472be96e6patch
- https://git.kernel.org/stable/c/6f4c80a2a7e6d06753b89a578b710a2499a5e62bpatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.