CVE-2026-99128

Source
https://cve.org/CVERecord?id=CVE-2026-99128
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99128.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99128
Downstream
Published
2026-10-28T10:34:42Z
Modified
2026-11-01T02:31:04Z
Summary
sctp: validate chunk length in the inqueue parser
Details

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.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99128.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
bbd0d59809f923ea2b540cbd781b32110e249f6e
Fixed
cc4a4f1d6b6d725438dc37b97f03d95ed9feb63f
Fixed
b0dbd53b242609c88e81b0a49093bdbef5d5a418
Fixed
d28ea1a62e27210d8ea3cf496dfae85dbdd7b84f
Fixed
5a7ee52589dae36c93dc64d7a97c5ded84618572
Fixed
e0fb7fe180488a5afa2e91509ea838e8df8cb771
Fixed
40507f59f230dcf60ae13cb48d34f8c6e9f40659
Fixed
9ac57e4c62e93c287b36080e5da3645690549990
Fixed
6cfc1b90cb86f4aabc69fb8e30128e07e2cdfa3a

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99128.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.6.24
Fixed
5.10.273
Type
ECOSYSTEM
Events
Introduced
5.11.0
Fixed
5.15.224
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.191
Type
ECOSYSTEM
Events
Introduced
6.2.0
Fixed
6.6.161
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.115
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.59
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.2.13

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99128.json"