9.8

CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling

Modified
AliasesUBUNTU-CVE-2026-52924DEBIAN-CVE-2026-52924CGA-3vfp-gm66-55cp
Published 24-06-2026Last modified 19-10-2026

Vulnerability summary

CVE-2026-52924 is a critical (CVSS 9.8) Use After Free vulnerability in linux. EPSS estimates a 0.66% chance of exploitation in the next 30 days, higher than 51.5% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 9.8 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
9.8/10
010
Critical · v3.1 (CVE.org)
EPSS score
0.66%
0%100%
Low · +0.13 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 68 · Related 55

Timeline

  1. 24-06-2026
    PublishedVulnerability first disclosed.
  2. 19-10-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

6 scores · 5 sources · 2 versions

EPSS trend

Probability

0.66%

Chance of exploitation in the next 30 days

Percentile

52%

Versus all other CVEs

30-day change

Increase +0.13 pp

From 0.53% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu167 products
  • linux< 4.15.0-254.266 | < 5.4.0-234.254 | < 5.15.0-187.197 | < 6.8.0-137.137 | All versions (No fix recorded) | < 7.0.0-29.29
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 4.15.0-1195.208 | < 5.4.0-1162.173 | < 5.15.0-1113.120 | < 6.8.0-1062.65 | All versions (No fix recorded) | < 7.0.0-1010.10
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard6 products
  • linux-azure-6.18< 6.18.38-r0
  • linux-gcp-6.18< 6.18.38-r0
  • linux-gcp-6.18-bootc-boot-installed< 6.18.38-r0
  • linux-qemu-6.18< 6.18.38-r0
  • linux-qemu-6.18-bootc-boot-installed< 6.18.38-r0
Linux2 products
  • linux≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < 84b7a319105db2f917ccdcf502bdc866082b1285 | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < f46e1d1a758878f0d22c4fbbd1bf42bb7165d1e8 | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < 3c0741a441a7df7099d7ca6a64a6a0de09c677c8 | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < 2afc9e684dc7fecf73db1edc937ebbc47b4b68dc | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < 1d4652f677906a64487c13f9ace54b0eb263b5d0 | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < a6207349e703cfc04756a4d16dec9176135813a5 | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < 83ade59e5da365f4bf8bce72c5a38774202b442f | ≥ 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, < e374b22e9b07b72a25909621464ff74096151bfb | 4.15
  • linux_kernel≥ 4.15, < 5.10.259 | ≥ 5.11, < 5.15.210 | ≥ 5.16, < 6.1.176 | ≥ 6.2, < 6.6.143 | ≥ 6.7, < 6.12.94 | ≥ 6.13, < 6.18.36 | ≥ 6.19, < 7.0.13 | 7.1:rc1 | 7.1:rc2 | 7.1:rc3 | 7.1:rc4 | 7.1:rc5 | 7.1:rc6
Debian1 product
  • linux< 6.1.176-1 | < 6.12.94-1 | < 7.0.13-1

4 vendors · 176 products

References

60 links
Show all 60 references