← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-52924

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-52924

Key Details

CVECVE-2026-52924
CVSS Score / Version
9.8 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, and Red Hat Enterprise Linux 9
Classified as
CWE-416 (Use After Free)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
Red HatRed Hat Enterprise Linux 10
Red HatRed Hat Enterprise Linux 8
Red HatRed Hat Enterprise Linux 9
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's and Red Hat's web pages for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-52924
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-52924
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.