CVE-2026-99758 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

sctp: account for chunk padding in sctp_init_cause()

sctp_init_cause() accepts a chunk when skb_tailroom() can hold the cause header and the payload. sctp_addto_chunk() then writes 0-3 bytes of padding before that header so the chunk stays 4-byte aligned. The check does not include the padding, and the following skb_put() calls skb_over_panic() from softirq.

Count the padding sctp_addto_chunk() is about to write. The cause length on the wire stays the header plus the payload.

Found by LLM inspection, triggered and tested the fix.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The Stream Control Transmission Protocol implementation within the Linux kernel contains a critical buffer management flaw in the sctp_init_cause function that leads to an out-of-bounds write condition during packet construction. This vulnerability arises from an incorrect calculation of available space within the socket buffer when preparing SCTP chunks for transmission or error reporting. The core issue lies in how the code verifies whether sufficient memory is allocated before writing data into the network buffer structure, specifically failing to account for mandatory alignment padding required by the protocol specification.

SCTP messages are structured with specific header fields followed by payload data and potentially trailing padding bytes to ensure 4-byte alignment as mandated by RFC 3286. When sctp_init_cause is invoked, it receives a pointer to an sk_buff structure representing the network buffer. The function checks if the remaining tailroom in this buffer can accommodate both the cause header and its payload using skb_tailroom. However, this check neglects the additional bytes that sctp_addto_chunk will subsequently write for padding purposes. This oversight means the validation passes even when there is insufficient space to complete the full chunk construction including alignment requirements.

The operational consequence of this miscalculation manifests as a kernel panic triggered by skb_over_panic during softirq processing. When execution proceeds past the flawed check, sctp_addto_chunk attempts to write padding bytes that exceed the allocated buffer boundaries. This results in memory corruption within the network stack subsystems which are operating with elevated privileges and interrupt context constraints. The resulting crash disrupts network connectivity for affected systems and can potentially be leveraged by local attackers or remote entities sending malformed SCTP packets to cause denial of service conditions against vulnerable kernel instances.

This vulnerability aligns closely with CWE-131, the Incorrect Calculation of Buffer Size category, where software fails to properly account for all necessary components when determining buffer capacity requirements. From a threat modeling perspective utilizing MITRE ATT&CK frameworks, this flaw facilitates Denial of Service via resource exhaustion or system crash mechanisms often categorized under T1499 endpoints denial of service techniques that exploit implementation flaws in network protocol stacks rather than application logic errors directly.

Mitigation strategies primarily involve applying vendor-provided kernel patches that correct the arithmetic operation within sctp_init_cause to include padding bytes in the space availability check. System administrators should ensure their Linux distributions are updated with security fixes addressing this specific SCTP buffer handling defect until upstream kernels incorporate the corrected logic permanently. Additionally, deploying network intrusion detection systems capable of identifying malformed SCTP packet structures may provide an additional layer of defense by blocking potentially triggering traffic before it reaches vulnerable kernel components processing these protocol elements.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00168

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!