CVE-2026-99758: sctp: account for chunk padding in sctp_init_cause()

Published Nov 20, 2026
·
Updated

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

sctp: account for chunk padding in sctpinitcause()

sctpinitcause() accepts a chunk when skbtailroom() can hold the cause header and the payload. sctpaddtochunk() 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 skbput() calls skboverpanic() from softirq.

Count the padding sctpaddtochunk() 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.

Affected Software

7 affected componentsFixes available
linux/kernel>=4.18.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required to trigger the failure?

The SCTP code must call sctp_init_cause() with tailroom sufficient for the cause header and payload but insufficient once the 0-3 bytes of alignment padding written by sctp_addto_chunk() are included. The subsequent skb_put() can then trigger skb_over_panic() in softirq context.

2

What is the practical impact of successful triggering?

The described result is an skb_over_panic() from softirq after an undersized tailroom check. The provided data does not establish remote reachability, required privileges, or a broader impact beyond this kernel failure condition.

3

How is the issue fixed?

The fix includes the alignment padding that sctp_addto_chunk() will write when checking available skb tailroom in sctp_init_cause(). The cause length sent on the wire remains the cause header plus payload and does not include the padding.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203