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)
EPSS
17.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 2026

Advisory Details (10)

Auto-updated Jun 30, 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(1)

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

Data Freshness Timeline

(refreshed 125× in last 7d / 147× 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 147 total refreshes for this CVE.

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

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 June 30, 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 17.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.