SECUFOCUSNOW
Home›CVE index›CVE-2026-64551
Review reviewCritical

CVE-2026-64551

Linux

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 c...

CVSS
9.1
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.28
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 9.1

Vulnerability overview

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 c...

Affected product and versions

Product
Linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6022da37786701df1fc5dd946a6dcba59d5473b1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 861f884f5471632c731cbbd612a1c072e391a624, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 588706ebaf8cdb4a4161602949eba365514b1db1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a257b41ddfe9e327b26581ad2777f04b23ac73f5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 08a8f2d13f703924316e9aeac863a88ef50990c7, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ebe0a55d954fa8da383b6192edb8f763dcb002d5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bbd6b2ea966cf57b6ae095cf5a8dbc993cd197a0, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1cd23ca80784223fa2204e16203f754da4e821f8, >= 2.6.12
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CWE
Not available