KernelScan.io

HIGH Introduced in 4.12

sctp Reconf Underflow

CVE-2026-89476

CVSS 7.5 / 10.0 NVD

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

KernelScan AI9.8CRITICAL

01

In the Linux kernel, the following vulnerability has been resolved: sctp: fix stream->outcnt underflow on duplicate RECONF responses A cached RECONF chunk may contain more than one request parameter. A duplicate response can therefore find and process the same ADD_OUT request again while another parameter is still outstanding, rolling back outcnt twice and possibly underflowing it. Track outstanding request types as bits and clear each bit after its first response. Later responses for the same request are then ignored.

02

Engine v0.6.0

Risk summary

A remote attacker who can send SCTP packets to a host with an active SCTP association can trigger an integer underflow in the stream output count by sending duplicate RECONF response chunks. This underflow can lead to out-of-bounds memory access in the kernel, potentially enabling code execution, data corruption, or a kernel crash. Any system running a kernel with SCTP support and exposed to untrusted network peers is at risk.

Affectednet/sctp/stream.c (SCTP stream reconfiguration)

Vulnerability analysis

The SCTP stream reconfiguration mechanism tracks how many RECONF request parameters are outstanding using a simple counter. When a cached RECONF chunk bundles multiple request parameters, a duplicate response can cause the same request to be processed again, decrementing the counter and rolling back the stream output count a second time. This double rollback can underflow the output count, which is used to size stream array operations, leading to out-of-bounds memory access. The fix replaces the counter with a bitmask where each request type occupies one bit; the bit is cleared after the first matching response is processed, so subsequent duplicate responses for the same request type are ignored. The vulnerability is reachable from the network by any SCTP peer that can send RECONF response chunks to a host with an active SCTP association—no special privileges are required on the attacker's side, only network connectivity to the target.

03

BranchIntroducedFixed inPatch commit
5.104.125.10.270041f7df5a929
5.154.125.15.22159f61c39cb99
6.14.126.1.188793519e34386
6.124.126.12.1092d867663c563
6.184.126.18.50d02a5794c3de
6.64.126.6.157092acd3c55a4
7.24.127.2.48320cbd81bc2
mainline4.127.33faf13aff243
cip/5.104.125.10.271-cip78041f7df5a929
cip/6.14.126.1.189-cip61793519e34386
cip/6.1-rt4.126.1.189-cip61-rt32793519e34386
cip/6.124.126.12.111-cip322d867663c563

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip136)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip136-rt50)