KernelScan.io

HIGH Introduced in 4.16

sctp OutputStream NullDeref

CVE-2026-99165

CVSS 7.5 / 10.0 KernelScan AI

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

01

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate output stream after association connect wait When message interleaving is enabled, the first send waits for association establishment before building its data chunks. The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count. sctp_stream_init() then frees the extension of every removed stream. The sender resumes with the stream that it checked before the wait. If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension. Fatal-oops policies then panic the host. KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace: sctp_primitive_SEND sctp_sendmsg_to_asoc sctp_sendmsg A range check alone is insufficient. Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink. The stream can then be in range while its extension remains NULL. The send-buffer wait has the same issue. Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock. Once the lock is reacquired, the validation remains stable through data creation and queueing. If validation fails after the connect wait, the auto-created association is already established. Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.

02

Engine v0.9.0

Risk summary

A remote SCTP peer can trigger a kernel NULL pointer dereference and panic by advertising fewer inbound streams during the handshake when message interleaving is enabled. The vulnerability affects any system with SCTP support that initiates connections to untrusted peers.

Affectednet/sctp/socket.c (sctp)

Vulnerability analysis

When message interleaving is enabled, the first SCTP send waits for association establishment before building data chunks. During this wait the socket lock is dropped, allowing handshake processing to reduce the output stream count to the peer-advertised inbound stream count and free the extensions of removed streams. The sender resumes with a stream it validated before the wait, but if the peer removed that stream, the output queue code later dereferences its now-NULL extension, causing a kernel panic. The fix factors the stream range and extension checks into a helper and re-validates after each wait that releases the socket lock, ensuring the stream remains valid through data creation and queueing. A remote attacker only needs to act as an SCTP peer advertising a low inbound stream count; a local user merely initiates the connection, requiring no special privileges.

03

BranchIntroducedFixed inPatch commit
5.104.165.10.27326af2969b29c
5.154.165.15.224b925652ba3a3
6.14.166.1.191504bdf55438a
6.124.166.12.11584f741b7bb39
6.184.166.18.5977a63d1b813b
6.64.166.6.161994694a2d461
7.24.167.2.13fd56ac95ec31
mainline4.167.3b7ad72414c67
cip/6.124.166.12.117-cip3584f741b7bb39

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.117-cip35
cip/6.1Affected — no CIP fix yet (latest 6.1.190-cip62)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)
cip/5.10Affected — no CIP fix yet (latest 5.10.272-cip79)
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.272-cip79-rt35)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip137)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip137-rt51)