Skip to main content

Linux Kernel CVE-2026-52924

| EUVDEUVD-2026-38727 CRITICAL
Expired Pointer Dereference (CWE-825)
2026-06-24 Linux GHSA-v4hw-q98x-8jmm
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.9 MEDIUM

Remotely triggerable (AV:N, PR:N) but needs a precise SCTP handshake/state-machine race with queued data (AC:H); demonstrated impact is a kernel crash, so A:H with C/I:N.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
7.0 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Red Hat
7.0 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 08:24 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
9.8 (CRITICAL)
Patch available
Jun 24, 2026 - 09:16 EUVD
CVE Published
Jun 24, 2026 - 07:14 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 07:14 cve.org
CRITICAL 9.8

DescriptionCVE.org

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

sctp: purge outqueue on stale COOKIE-ECHO handling

sctp_stream_update() is only invoked when the association is moved into COOKIE_WAIT during association setup/reconfiguration. In this path, the outbound stream scheduler state (stream->out_curr) is expected to be clean, since no user data should have been transmitted yet unless the state machine has already partially progressed.

However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a Stale Cookie ERROR is received, the association is rolled back from COOKIE_ECHOED to COOKIE_WAIT. In this scenario, user data may already have been queued and even bundled with the COOKIE-ECHO chunk.

During the rollback, sctp_stream_update() frees the old stream table and installs a new one, but it does not invalidate stream->out_curr. As a result, out_curr may still point to a freed sctp_stream_out entry from the previous stream state.

Later, SCTP scheduler dequeue paths (FCFS, RR, PRIO, etc.) rely on stream->out_curr->ext, which can lead to use-after-free once the old stream state has been released via sctp_stream_free().

This results in crashes such as (reported by Yuqi):

BUG: KASAN: slab-use-after-free in sctp_sched_fcfs_dequeue+0x13a/0x140 Read of size 8 at addr ff1100004d4d3208 by task mini_poc/9312 CPU: 1 UID: 1001 PID: 9312 Comm: mini_poc Not tainted 7.1.0-rc1-00305-gbd3a4795d574 #5 PREEMPT(full) sctp_sched_fcfs_dequeue+0x13a/0x140 sctp_outq_flush+0x1603/0x33e0 sctp_do_sm+0x31c9/0x5d30 sctp_assoc_bh_rcv+0x392/0x6f0 sctp_inq_push+0x1db/0x270 sctp_rcv+0x138d/0x3c10

Fix this by fully purging the association outqueue when handling the Stale Cookie case. This ensures all pending transmit and retransmit state is dropped, and any scheduler cached pointers are invalidated, making it safe to rebuild stream state during COOKIE_WAIT restart.

Updating only stream->out_curr would be insufficient, since queued and retransmittable data would still reference the old stream state and trigger later use-after-free in dequeue paths.

AnalysisAI

Use-after-free in the Linux kernel SCTP stack (net/sctp) allows a remote peer to crash the kernel by forcing an association to roll back from COOKIE_ECHOED to COOKIE_WAIT via a Stale Cookie ERROR. When sctp_stream_update() rebuilds the stream table during this rollback it leaves the scheduler's cached stream->out_curr pointer referencing freed memory, so the next scheduler dequeue (FCFS/RR/PRIO) dereferences a dangling sctp_stream_out entry. The flaw is tagged as Denial of Service, carries an NVD CVSS of 9.8, but has a low EPSS of 0.17% (6th percentile); no public exploit identified at time of analysis and it is not listed in CISA KEV.

Technical ContextAI

The vulnerability lives in the kernel's SCTP (Stream Control Transmission Protocol, RFC 9260) transport implementation, specifically the 4-way COOKIE handshake state machine and the outbound stream scheduler. During association setup the handler sctp_sf_do_5_2_6_stale() processes a received Stale Cookie ERROR by rolling the association back from COOKIE_ECHOED to COOKIE_WAIT and calling sctp_stream_update(), which frees the old per-stream output table (sctp_stream_out) and installs a new one. Because user data and even data bundled with the COOKIE-ECHO chunk may already have been queued, the scheduler's cached pointer stream->out_curr is left pointing at the freed entry; subsequent dequeue paths read out_curr->ext, producing a slab-use-after-free (KASAN-confirmed) - a classic CWE-416 Use-After-Free, though NVD lists the CWE as N/A. The fix fully purges the association outqueue during the stale-cookie path so all pending transmit/retransmit state and cached scheduler pointers are invalidated before the stream state is rebuilt. CPE coverage is the generic cpe:2.3:a:linux:linux:*, so affected scope is the upstream kernel codebase rather than a single distribution.

RemediationAI

Vendor-released patch: upgrade to a fixed kernel point release - 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 7.0.13, 6.18.36, or mainline 7.1, choosing the fixed release matching your branch - and reboot; the corresponding stable commits are at https://git.kernel.org/stable/c/3c0741a441a7df7099d7ca6a64a6a0de09c677c8 (and the sibling hashes listed in the references). For distribution kernels, apply the vendor kernel update that references CVE-2026-52924 rather than building from source. Where immediate patching is not possible, the most effective compensating control is to disable SCTP if it is not required: blacklist the module (e.g. 'install sctp /bin/true' in modprobe.d) so it cannot be auto-loaded, which fully removes the attack surface but breaks any SCTP-dependent application (common in telecom/SS7/Diameter stacks). If SCTP is needed, restrict SCTP reachability with firewall rules (block IP protocol 132 from untrusted networks) and limit peers to trusted endpoints - this reduces but does not eliminate risk from a malicious or spoofing peer, since the trigger comes from a peer-sent Stale Cookie ERROR during association setup.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.177 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.155 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.206 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.152 Affected
Container suse/sle-micro-rancher/5.3:latest Container suse/sle-micro-rancher/5.4:5.4.4.5.149 Affected
Container suse/sle-micro/base-5.5:2.0.4-5.8.296 Affected
Container suse/sle-micro/kvm-5.5:2.0.4-3.5.570 Affected

Share

CVE-2026-52924 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy