CVE-2026-52924

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
25.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: redhat.
redhat

2492095 – (CVE-2026-52924) CVE-2026-52924 kernel: sctp: purge outqueue on stale COOKIE-ECHO handling

https://bugzilla.redhat.com/show_bug.cgi?id=2492095
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-52924
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f46e1d1a758878f0d22c4fbbd1bf42bb7165d1e8
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e374b22e9b07b72a25909621464ff74096151bfb
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6207349e703cfc04756a4d16dec9176135813a5
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84b7a319105db2f917ccdcf502bdc866082b1285
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83ade59e5da365f4bf8bce72c5a38774202b442f
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c0741a441a7df7099d7ca6a64a6a0de09c677c8
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2afc9e684dc7fecf73db1edc937ebbc47b4b68dc
generic

sctp: purge outqueue on stale COOKIE-ECHO handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d4652f677906a64487c13f9ace54b0eb263b5d0

Vendor Advisories for CVE-2026-52924(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 232× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 232 total refreshes for this CVE.

  1. 2026-07-23 03:19 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 03:33 UTCVendor advisory
  9. 2026-07-17 03:33 UTCGHSA enrichment
  10. 2026-07-16 23:04 UTCVendor advisory
  11. 2026-07-16 23:04 UTCGHSA enrichment
  12. 2026-07-16 18:45 UTCVendor advisory
  13. 2026-07-16 18:45 UTCGHSA enrichment
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 14:19 UTCGHSA enrichment
  16. 2026-07-16 09:57 UTCVendor advisory
  17. 2026-07-16 09:57 UTCGHSA enrichment
  18. 2026-07-16 05:37 UTCVendor advisory
  19. 2026-07-16 05:37 UTCGHSA enrichment
  20. 2026-07-16 01:18 UTCVendor advisory
  21. 2026-07-16 01:18 UTCGHSA enrichment
  22. 2026-07-15 20:58 UTCVendor advisory
  23. 2026-07-15 20:58 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 16:25 UTCVendor advisory
  2. 2026-07-15 16:25 UTCGHSA enrichment
  3. 2026-07-15 12:05 UTCVendor advisory
  4. 2026-07-15 12:05 UTCGHSA enrichment
  5. 2026-07-15 06:13 UTCVendor advisory
  6. 2026-07-15 06:13 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-15 01:38 UTCVendor advisory
  10. 2026-07-15 01:38 UTCGHSA enrichment
  11. 2026-07-14 21:19 UTCVendor advisory
  12. 2026-07-14 21:19 UTCGHSA enrichment
  13. 2026-07-14 17:00 UTCVendor advisory
  14. 2026-07-14 17:00 UTCGHSA enrichment
  15. 2026-07-14 12:40 UTCVendor advisory
  16. 2026-07-14 12:40 UTCGHSA enrichment
  17. 2026-07-14 08:20 UTCVendor advisory
  18. 2026-07-14 08:20 UTCGHSA enrichment
  19. 2026-07-14 03:39 UTCVendor advisory
  20. 2026-07-14 03:39 UTCGHSA enrichment
  21. 2026-07-13 23:19 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 18:59 UTCGHSA enrichment
  24. 2026-07-13 14:39 UTCGHSA enrichment
  25. 2026-07-13 10:20 UTCGHSA enrichment
  26. 2026-07-13 06:13 UTCEPSS rescore
  27. 2026-07-13 06:13 UTCEPSS rescore
  28. 2026-07-13 06:01 UTCVendor advisory
  29. 2026-07-13 06:00 UTCGHSA enrichment
  30. 2026-07-13 01:40 UTCVendor advisory
  31. 2026-07-13 01:40 UTCGHSA enrichment
  32. 2026-07-12 21:21 UTCVendor advisory
  33. 2026-07-12 21:21 UTCGHSA enrichment
  34. 2026-07-12 16:25 UTCVendor advisory
  35. 2026-07-12 16:24 UTCGHSA enrichment
  36. 2026-07-12 12:04 UTCVendor advisory
  37. 2026-07-12 12:04 UTCGHSA enrichment
  38. 2026-07-12 07:43 UTCVendor advisory
  39. 2026-07-12 07:43 UTCGHSA enrichment
  40. 2026-07-12 05:46 UTCEPSS rescore
  41. 2026-07-12 03:23 UTCVendor advisory
  42. 2026-07-12 03:23 UTCGHSA enrichment
  43. 2026-07-11 23:03 UTCVendor advisory
  44. 2026-07-11 23:03 UTCGHSA enrichment
  45. 2026-07-11 18:44 UTCVendor advisory
  46. 2026-07-11 18:44 UTCGHSA enrichment
  47. 2026-07-11 14:25 UTCVendor advisory
  48. 2026-07-11 14:25 UTCGHSA enrichment
  49. 2026-07-11 09:41 UTCVendor advisory
  50. 2026-07-11 09:41 UTCGHSA enrichment
  51. 2026-07-11 08:27 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-11 05:21 UTCVendor advisory
  54. 2026-07-11 05:21 UTCGHSA enrichment
  55. 2026-07-11 01:02 UTCVendor advisory
  56. 2026-07-11 01:01 UTCGHSA enrichment
  57. 2026-07-10 20:42 UTCVendor advisory
  58. 2026-07-10 20:41 UTCGHSA enrichment
  59. 2026-07-10 16:20 UTCVendor advisory
  60. 2026-07-10 16:20 UTCGHSA enrichment
  61. 2026-07-10 11:53 UTCVendor advisory
  62. 2026-07-10 11:53 UTCGHSA enrichment
  63. 2026-07-10 07:33 UTCVendor advisory
  64. 2026-07-10 07:33 UTCGHSA enrichment
  65. 2026-07-10 03:14 UTCVendor advisory
  66. 2026-07-10 03:14 UTCGHSA enrichment
  67. 2026-07-09 22:55 UTCVendor advisory
  68. 2026-07-09 22:55 UTCGHSA enrichment
  69. 2026-07-09 19:10 UTCEPSS rescore
  70. 2026-07-09 19:10 UTCEPSS rescore
  71. 2026-07-09 18:35 UTCVendor advisory
  72. 2026-07-09 18:35 UTCGHSA enrichment
  73. 2026-07-09 14:10 UTCVendor advisory
  74. 2026-07-09 14:10 UTCGHSA enrichment
  75. 2026-07-09 09:50 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-52924?
CVE-2026-52924 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: purge outqueue on stale COOKIE-ECHO handling sctpstreamupdate() is only invoked when the association is moved into COOKIE_WAIT during association setup/reconfiguration. In this path, the outbound stream scheduler state…
When was CVE-2026-52924 disclosed?
CVE-2026-52924 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52924 actively exploited?
CVE-2026-52924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52924?
CVE-2026-52924 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52924?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52924, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52924

Explore →

Is Your Infrastructure Affected by CVE-2026-52924?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.