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.
Published: 2026-10-28
Score: n/a
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Patch immediately
AI Analysis

Impact

The Linux kernel contains a flaw in the SCTP inqueue parser where it accepts chunks with declared lengths shorter than the required four‑byte header. When an ASCONF chunk is processed under the association’s SCTP‑AUTH policy, the flawed function can repeatedly return the same malformed chunk, causing the receive softirq to lock up and drain the system’s watchdog health checks. The impact is a denial of service that can be forced remotely by any SCTP peer that can establish an association with the vulnerable kernel. Affected systems are Linux distributions running kernels that have the CONFIG_IP_SCTP option enabled together with SCTP’s address‑configuration and authentication features (net.sctp.addip_enable=1, net.sctp.auth_enable=1). The vulnerability is specific to the kernel itself, so all installations that include the SCTP stack and are compiled with the mentioned options are potentially impacted. No particular kernel release number is listed, but the fix is referenced as commit f967455fb2a5. The known exploitability is limited to remote peers that can initiate SCTP associations. While no EPSS score is available and the vulnerability is not listed in CISA’s KEV catalog, the ciphertext description indicates that a zero‑length ASCONF packet can trigger the lockup in a KVM guest. The attack does not require application credentials or an AUTH key and therefore is relatively easy to execute against a properly configured kernel.

Affected Systems

Linux kernel installations that have the SCTP stack enabled (CONFIG_IP_SCTP) together with the address‑configuration and authentication options turned on. Any distribution running a built kernel in this configuration is potentially affected, but no specific vendor or version details are provided.

Risk and Exploitability

The flaw enables a remote denial‑of‑service condition by causing softirq lockups. Because the attack does not require privileged credentials or special configuration beyond the enabled SCTP features, the likelihood of exploitation in environments that expose SCTP is considered moderate. The vulnerability is not yet in the CISA KEV catalog and no EPSS score is published, but the described reproduction shows realistic impact in virtualized guests. Consequently, administrators should assess whether SCTP is required in their environment and apply the patch as soon as possible.

Generated by OpenCVE AI on October 28, 2026 at 11:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel patch that includes the fix in commit f967455fb2a5.
  • Update to a kernel release that contains the SCTP inqueue length validation fix.
  • If patching is not immediately possible, disable SCTP support by setting CONFIG_IP_SCTP off or by turning net.sctp.addip_enable and net.sctp.auth_enable to 0 to prevent the vulnerable code from running.

Generated by OpenCVE AI on October 28, 2026 at 11:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 28 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-682

Wed, 28 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
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.
Title sctp: validate chunk length in the inqueue parser
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-28T10:34:42.229Z

Reserved: 2026-09-25T10:25:14.394Z

Link: CVE-2026-99128

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-28T11:17:32.570

Modified: 2026-10-28T11:17:32.570

Link: CVE-2026-99128

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-28T11:45:09Z

Weaknesses