sctp: validate STALE_COOKIE cause length before reading staleness
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: validate STALE_COOKIE cause length before reading staleness When an ERROR chunk with a STALE_COOKIE cause is received in the COOKIE_ECHOED state, sctp_sf_do_5_2_6_stale() reads the 4-byte Measure of Staleness that follows the cause header: err = (struct sctp_errhdr *)(chunk->skb->data); stale = ntohl(*(__be32 )((u8 )err + sizeof(*err))); err is the first cause in the chunk, not the STALE_COOKIE cause that caused the dispatch, and nothing guarantees the staleness field is present. sctp_walk_errors() only requires a cause to be as long as the 4-byte header, so for a STALE_COOKIE cause of length 4 the read runs past the cause, and for a minimal ERROR chunk past skb->tail. The value is echoed to the peer in the Cookie Preservative of the reply INIT, leaking uninitialized memory. sctp_sf_cookie_echoed_err() already walks to the STALE_COOKIE cause, so check its length there and pass it to sctp_sf_do_5_2_6_stale(), which reads that cause instead of the first one. A STALE_COOKIE cause too short to hold the staleness field is discarded. The read is reachable by any peer that can drive an association into COOKIE_ECHOED, including an unprivileged process using a raw SCTP socket in a user and network namespace.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 6022da37786701df1fc5dd946a6dcba59d5473b1; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 861f884f5471632c731cbbd612a1c072e391a624; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 588706ebaf8cdb4a4161602949eba365514b1db1; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a257b41ddfe9e327b26581ad2777f04b23ac73f5; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 08a8f2d13f703924316e9aeac863a88ef50990c7; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in ebe0a55d954fa8da383b6192edb8f763dcb002d5; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 1cd23ca80784223fa2204e16203f754da4e821f8
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/6022da37786701df1fc5dd946a6dcba59d5473b1
- stable/c/861f884f5471632c731cbbd612a1c072e391a624
- stable/c/588706ebaf8cdb4a4161602949eba365514b1db1
- stable/c/a257b41ddfe9e327b26581ad2777f04b23ac73f5
- stable/c/08a8f2d13f703924316e9aeac863a88ef50990c7
- stable/c/ebe0a55d954fa8da383b6192edb8f763dcb002d5
- stable/c/bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0
- stable/c/1cd23ca80784223fa2204e16203f754da4e821f8