CVE-2026-98123
Description
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A remote attacker can cause a Denial of Service (DoS) by sending a specially crafted network packet during an active SCTP connection. A discrepancy in how parameter padding is processed causes the system to interpret misaligned data and enter an infinite loop, resulting in a CPU soft lockup that makes the system unresponsive. In certain conditions, missing length validation can also trigger an out-of-bounds memory read.
Statement
An inconsistency in SCTP ASCONF ACK parameter iteration can let a remote peer desynchronize verification from later parameter consumption. An odd length parameter can make sctp_get_asconf_response interpret attacker controlled bytes at a misaligned offset, and a decoded zero length can prevent the softirq loop from making progress. This can cause a CPU soft lockup and denial of service on a host with SCTP ADD IP enabled, an established association, and an outstanding ASCONF request. For the CVSS the PR:N value is used because a network peer can trigger the condition without local code execution or privileges on the target. The issue is remotely reachable over SCTP, although practical exposure depends on SCTP being permitted by network firewalls and on the required association state. A separate short ERR_CAUSE parameter can cause a bounded out of bounds read across the logical parameter boundary, but the read remains inside the received skb and does not provide a demonstrated kernel memory disclosure or write primitive. Impact is therefore denial of service without a supported privilege escalation path.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | 5.5 | N/A |
| Attack Vector | Network | Local | N/A |
| Attack Complexity | High | Low | N/A |
| Privileges Required | None | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification
An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.