CVE-2026-72413

sctp: fix err_chunk memory leaks in INIT handling

N/A
Published: August 15, 2026 at 05:56 AM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: fix err_chunk memory leaks in INIT handling When sctp_verify_init() encounters unrecognized parameters, it allocates an err_chunk to report them. However, this chunk is leaked in several code paths: 1. In sctp_sf_do_5_1B_init(), if security_sctp_assoc_request() fails after sctp_verify_init() has populated err_chunk, the function returns immediately without freeing it. 2. In sctp_sf_do_unexpected_init(), the same leak occurs on the security_sctp_assoc_request() failure path. 3. In sctp_sf_do_unexpected_init(), on the success path after copying unrecognized parameters to the INIT-ACK, the function returns without freeing err_chunk, unlike sctp_sf_do_5_1B_init() which properly frees it. Fix all three leaks by adding sctp_chunk_free(err_chunk) calls before returning in the error paths and on the success path in sctp_sf_do_unexpected_init().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 6.1.1892.6.12 ≤ v < 6.12.1112.6.12 ≤ v < 6.18.532.6.12 ≤ v < 6.6.1582.6.12 ≤ v < 7.1.52.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 1cae40d423a2042c7970f29c00028951ec20db8a (fixed)
Vendor states this is fixed in 43ddbcdc0ed74a8fba4aff5e623ace8135411b93 (fixed)
Vendor states this is fixed in 6acedac7a14af71cfe25024ead28e16a070899e4 (fixed)
Vendor states this is fixed in 94f55994e19e8f0676990b9d5015b58ab6a97e00 (fixed)
Vendor states this is fixed in 9f58a0a4d6c2ed5d341bba64f058f15d1b0c36f2 (fixed)
Vendor states this is fixed in a8e6a839c0e7ca1da752faaab51e2eafb17483a4 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card