In the Linux kernel, the following vulnerability has been resolved: sctp: validate STALE_COOKIE cause length before reading staleness When an ERROR… (CVE-2026-64551)
A critical vulnerability in the Linux kernel SCTP implementation allows an unprivileged peer to leak uninitialized kernel memory. The flaw occurs when processing an ERROR chunk with a STALE_COOKIE cause in the COOKIE_ECHOED state, where the kernel reads beyond the intended cause length, potentially leaking sensitive data. This memory leak can be triggered by any peer capable of driving an association into COOKIE_ECHOED, including unprivileged processes using raw SCTP sockets. The vulnerability has been resolved by validating the STALE_COOKIE cause length before reading the staleness field and discarding causes that are too short.
AI Analysis
Technical Summary
The Linux kernel SCTP subsystem improperly reads a 4-byte Measure of Staleness field following a STALE_COOKIE cause header in an ERROR chunk during the COOKIE_ECHOED state. The code incorrectly reads from the first cause in the chunk rather than the STALE_COOKIE cause, which may be shorter than expected. This leads to out-of-bounds reads past the cause or even past the skb tail, leaking uninitialized kernel memory to the peer in the Cookie Preservative of the reply INIT. The vulnerability is reachable by any peer that can drive an association into COOKIE_ECHOED, including unprivileged users with raw SCTP socket access. The fix involves checking the length of the STALE_COOKIE cause before reading and discarding causes that are too short.
Potential Impact
An attacker can leak uninitialized kernel memory contents remotely without privileges, potentially exposing sensitive information. The vulnerability does not affect integrity but impacts confidentiality and availability due to the kernel reading out-of-bounds memory and possible kernel instability. The CVSS vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity impact, and high availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to raw SCTP sockets to trusted users to prevent unprivileged processes from exploiting this vulnerability. Monitor vendor channels for updates and apply patches promptly once released.
In the Linux kernel, the following vulnerability has been resolved: sctp: validate STALE_COOKIE cause length before reading staleness When an ERROR… (CVE-2026-64551)
Description
A critical vulnerability in the Linux kernel SCTP implementation allows an unprivileged peer to leak uninitialized kernel memory. The flaw occurs when processing an ERROR chunk with a STALE_COOKIE cause in the COOKIE_ECHOED state, where the kernel reads beyond the intended cause length, potentially leaking sensitive data. This memory leak can be triggered by any peer capable of driving an association into COOKIE_ECHOED, including unprivileged processes using raw SCTP sockets. The vulnerability has been resolved by validating the STALE_COOKIE cause length before reading the staleness field and discarding causes that are too short.
CVSS v3.1
Score 9.1critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel SCTP subsystem improperly reads a 4-byte Measure of Staleness field following a STALE_COOKIE cause header in an ERROR chunk during the COOKIE_ECHOED state. The code incorrectly reads from the first cause in the chunk rather than the STALE_COOKIE cause, which may be shorter than expected. This leads to out-of-bounds reads past the cause or even past the skb tail, leaking uninitialized kernel memory to the peer in the Cookie Preservative of the reply INIT. The vulnerability is reachable by any peer that can drive an association into COOKIE_ECHOED, including unprivileged users with raw SCTP socket access. The fix involves checking the length of the STALE_COOKIE cause before reading and discarding causes that are too short.
Potential Impact
An attacker can leak uninitialized kernel memory contents remotely without privileges, potentially exposing sensitive information. The vulnerability does not affect integrity but impacts confidentiality and availability due to the kernel reading out-of-bounds memory and possible kernel instability. The CVSS vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity impact, and high availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to raw SCTP sockets to trusted users to prevent unprivileged processes from exploiting this vulnerability. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m58p-8fjh-3whj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64551"]
- Ecosystems
- []
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a6b72d09c2644c7f8476a78
Added to database: 07/30/2026, 15:50:40 UTC
Last enriched: 07/30/2026, 19:26:54 UTC
Last updated: 07/31/2026, 20:17:48 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.