CVE-2026-99128

sctp: validate chunk length in the inqueue parser

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: validate chunk length in the inqueue parser SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header. When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up. A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1. On commit f967455fb2a5 ("seg6: reset IP6CB after IPv6 decapsulation"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared. Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6. The complete private reproducer and validation evidence are available directly to maintainers on request.

Key facts

Published
28 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.185% likely to be exploited in the next 30 days, higher than 8.183% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding cc4a4f1d6b6d725438dc37b97f03d95ed9feb63f (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding b0dbd53b242609c88e81b0a49093bdbef5d5a418 (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding d28ea1a62e27210d8ea3cf496dfae85dbdd7b84f (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding 5a7ee52589dae36c93dc64d7a97c5ded84618572 (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding e0fb7fe180488a5afa2e91509ea838e8df8cb771 (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding 40507f59f230dcf60ae13cb48d34f8c6e9f40659 (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding 9ac57e4c62e93c287b36080e5da3645690549990 (affected)
  • bbd0d59809f923ea2b540cbd781b32110e249f6e up to but excluding 6cfc1b90cb86f4aabc69fb8e30128e07e2cdfa3a (affected)
LinuxLinux
  • Default status: affected
  • 2.6.24 (affected)
  • 0 up to but excluding 2.6.24 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References