All Threat Alerts
criticalCVE Alert
CVE-2026-64551

Critical Vulnerability: CVE-2026-64551

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

Thursday, July 30, 2026Vulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2026-64551 is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Executive 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_st

Why It Matters

CVE-2026-64551 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.1/10

EPSS (Exploit Prediction): 0.2% probability of exploitation in the next 30 days.

๐Ÿ›ก๏ธWhat Defenders Should Check

  • Check if you are affected โ€” Review your asset inventory for products listed in CVE-2026-64551.
  • Apply available patches โ€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation โ€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2026-64551 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for SBOM-based CVE matching and Vulnios CVE feed continuous monitoring against your asset inventory. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2026-64551?

    CVE-2026-64551 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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

    Am I affected?

    Affected technology is listed in the Affected Products section above. If your asset inventory contains any of them, assume in-scope until you can prove otherwise.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2026-64551. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios