CVE-2026-64551: Linux kernel · sctp: validate STALE_COOKIE cause length before reading staleness
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in ebe0a55d954fa8da383b6192edb8f763dcb002d5 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in ebe0a55d954fa8da383b6192edb8f763dcb002d5, bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0, a257b41ddfe9e327b26581ad2777f04b23ac73f5 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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.
References
- git.kernel.org/stable/c/6022da37786701df1fc5dd946a6dcba59d5473b1 (opens in a new tab)
- git.kernel.org/stable/c/861f884f5471632c731cbbd612a1c072e391a624 (opens in a new tab)
- git.kernel.org/stable/c/588706ebaf8cdb4a4161602949eba365514b1db1 (opens in a new tab)
- git.kernel.org/stable/c/a257b41ddfe9e327b26581ad2777f04b23ac73f5 (opens in a new tab)
- git.kernel.org/stable/c/08a8f2d13f703924316e9aeac863a88ef50990c7 (opens in a new tab)
- git.kernel.org/stable/c/ebe0a55d954fa8da383b6192edb8f763dcb002d5 (opens in a new tab)
- git.kernel.org/stable/c/bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0 (opens in a new tab)
- git.kernel.org/stable/c/1cd23ca80784223fa2204e16203f754da4e821f8 (opens in a new tab)