PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-89477 Linux CVE debrief

A null pointer dereference vulnerability exists in the Linux kernel's SCTP (Stream Control Transmission Protocol) implementation. The vulnerability occurs when a stream reconfiguration request is completed on an untransmitted chunk, leading to a null pointer dereference. This vulnerability can be triggered by an unprivileged process that removes an address and then requests a stream reset, causing the kernel to panic from softirq. A remote peer can also trigger this vulnerability by sending a specially crafted packet.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-09-11
Advisory published
2026-09-11
Advisory updated
2026-09-11

Who should care

Linux kernel developers, administrators, and users who rely on SCTP protocol, as well as operators and security teams responsible for managing and securing Linux-based systems, should assess exposure and prioritize patching to prevent potential denial of service and remote code execution attacks.

Why it matters

CVE-2026-89477 is a null pointer dereference vulnerability in the Linux kernel's SCTP implementation. Defenders should care because it can lead to a denial of service and potentially allow for remote code execution, although further verification is needed. Linux kernel developers, administrators, and users who rely on SCTP protocol should assess exposure and prioritize patching.

  • Denial of Service (DoS) via null pointer dereference
  • Potential for remote code execution requires further verification
  • Need for patching and remediation prioritization

Technical summary

The vulnerability exists in the Linux kernel's SCTP implementation, specifically in the sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out(), and sctp_process_strreset_resp() functions. A null pointer dereference occurs when a stream reconfiguration request is completed on an untransmitted chunk. This can happen when an unprivileged process removes an address and then requests a stream reset, causing the kernel to panic from softirq. A remote peer can also trigger this vulnerability by sending a specially crafted packet. The vulnerability can be mitigated by reviewing and applying the provided kernel patches, restricting access to the SCTP protocol, and monitoring network traffic for suspicious

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the provided kernel patches to fix the vulnerability
  • Restrict access to the SCTP protocol to only trusted sources
  • Monitor network traffic for suspicious SCTP packets
  • Consider compensating controls for exposed systems while remediation is scheduled and verified
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by a null pointer dereference in the sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out(), and sctp_process_strreset_resp() functions. The vulnerability can be triggered by an unprivileged process or a remote peer.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-89477 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-89477

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-89477 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89477

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0ee697defc0594f1da810ed75d9d643fb46f5318

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/25419f516ea84b1e7d3d55aae5215ac86ece0c66

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2db9bfa3e27bdea15e05ea70b56bad3d21e570ec

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/77ea60f2d24002c308f224db44a4542c466489af

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.