Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64551sctp: validate STALE_COOKIE cause length before reading staleness

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64551, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Analyzed3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.51% · top 55% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6022da37786701df1fc5dd946a6dcba59d5473b1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 861f884f5471632c731cbbd612a1c072e391a624
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 588706ebaf8cdb4a4161602949eba365514b1db1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a257b41ddfe9e327b26581ad2777f04b23ac73f5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 08a8f2d13f703924316e9aeac863a88ef50990c7
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ebe0a55d954fa8da383b6192edb8f763dcb002d5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1cd23ca80784223fa2204e16203f754da4e821f8
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64551 badge
[![CVE-2026-64551](https://cveledger.app/badge/CVE-2026-64551.svg)](https://cveledger.app/cve/CVE-2026-64551)

Record last updated .