CVE-2026-89478

Description

A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. An authenticated attacker could exploit a timing window during the removal of an SCTP transport. This could lead to the system attempting to read from freed memory, potentially causing a denial of service or information disclosure.

Statement

An SCTP use after free can occur when a packet keeps a chunk.transport pointer while an authenticated ASCONF DEL-IP removes the same transport from the association. A DATA chunk from that packet can restore the removed transport into asoc peer last_data_from, and a later delayed SACK can carry the stale pointer into transport selection where freed transport state is read. This is a network reachable race condition with AC:H because the vulnerable window depends on packet backlog or direct receive timing around socket locking and transport removal. For the CVSS the PR:N is used for the paranoid score because a remote SCTP peer may trigger the path without local code execution on the target once it can reach and form the required association. If SCTP AUTH keys or association policy restrict the peer set, PR:L is a more realistic base interpretation. Impact is at least remote denial of service via kernel crash and in the paranoid case may include confidentiality and integrity impact because the primitive is UAF in kernel networking code.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A9.8
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.