CVE-2026-52929

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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: stream: fully roll back denied add-stream state

When ADD_OUT_STREAMS is denied, SCTP only shrinks the queued chunks and then lowers outcnt. That leaves removed stream metadata behind, so a later re-add can reuse a stale ext and hit a null-pointer dereference in the scheduler get path.

Fix the rollback by tearing down the removed stream state the same way other stream resizes do. Unschedule the current scheduler state, drop the removed stream ext state with sctp_stream_outq_migrate(), and then reschedule the remaining streams.

This keeps scheduler-private RR/FC/PRIO lists consistent while fully rolling back denied outgoing stream additions.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
31.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9662eb0401518f0b4681f10e7fbf688f504f24cf
generic

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7dd9a42b044aad2dbe037db1c1e2943582485b44
generic

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39dc2b0eb5371a669ebc9ec6072b9184eac95418
generic

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c6773b8c081509dcd5cd2954f2b02c50c00f151
generic

sctp: stream: fully roll back denied add-stream state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cd2dc6dce8ca47212cd306ccd52eb315ef3cf85

Vendor Advisories for CVE-2026-52929(2)

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

Data Freshness Timeline

(refreshed 50× in last 7d / 66× 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.

  1. 2026-07-06 19:56 UTCEG score recompute
  2. 2026-07-06 19:56 UTCVendor advisory
  3. 2026-07-06 19:55 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 07:41 UTCEG score recompute
  7. 2026-07-06 07:41 UTCVendor advisory
  8. 2026-07-06 07:41 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 19:51 UTCEG score recompute
  12. 2026-07-05 19:51 UTCVendor advisory
  13. 2026-07-05 19:51 UTCGHSA enrichment
  14. 2026-07-05 08:06 UTCEG score recompute
  15. 2026-07-05 08:06 UTCVendor advisory
  16. 2026-07-05 08:06 UTCGHSA enrichment
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 20:18 UTCEG score recompute
  19. 2026-07-04 20:18 UTCVendor advisory
  20. 2026-07-04 20:17 UTCGHSA enrichment
  21. 2026-07-04 08:31 UTCEG score recompute
  22. 2026-07-04 08:31 UTCVendor advisory
  23. 2026-07-04 08:31 UTCGHSA enrichment
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 20:43 UTCEG score recompute
Show 41 more
  1. 2026-07-03 20:43 UTCVendor advisory
  2. 2026-07-03 20:42 UTCGHSA enrichment
  3. 2026-07-03 08:56 UTCEG score recompute
  4. 2026-07-03 08:56 UTCVendor advisory
  5. 2026-07-03 08:56 UTCGHSA enrichment
  6. 2026-07-02 21:10 UTCEG score recompute
  7. 2026-07-02 21:10 UTCVendor advisory
  8. 2026-07-02 21:10 UTCGHSA enrichment
  9. 2026-07-02 09:25 UTCEG score recompute
  10. 2026-07-02 09:25 UTCVendor advisory
  11. 2026-07-02 09:25 UTCGHSA enrichment
  12. 2026-07-01 21:39 UTCEG score recompute
  13. 2026-07-01 21:39 UTCVendor advisory
  14. 2026-07-01 21:39 UTCGHSA enrichment
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 09:54 UTCEG score recompute
  17. 2026-07-01 09:54 UTCVendor advisory
  18. 2026-07-01 09:54 UTCGHSA enrichment
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 22:08 UTCEG score recompute
  21. 2026-06-30 22:08 UTCVendor advisory
  22. 2026-06-30 22:08 UTCGHSA enrichment
  23. 2026-06-30 10:22 UTCEG score recompute
  24. 2026-06-30 10:22 UTCVendor advisory
  25. 2026-06-30 10:22 UTCGHSA enrichment
  26. 2026-06-29 22:35 UTCEG score recompute▲ 7.50
  27. 2026-06-29 22:35 UTCVendor advisory
  28. 2026-06-29 22:35 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-27 03:38 UTCEG score recompute
  36. 2026-06-27 03:38 UTCGHSA enrichment
  37. 2026-06-27 03:08 UTCEPSS rescore
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-24 08:41 UTCEG score recompute
  41. 2026-06-24 08:40 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52929?
CVE-2026-52929 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: stream: fully roll back denied add-stream state When ADDOUTSTREAMS is denied, SCTP only shrinks the queued chunks and then lowers outcnt. That leaves removed stream metadata behind, so a later re-add can reuse a stale ext and…
When was CVE-2026-52929 disclosed?
CVE-2026-52929 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52929 actively exploited?
CVE-2026-52929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52929?
CVE-2026-52929 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-52929?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52929, 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-52929

Explore →

Is Your Infrastructure Affected by CVE-2026-52929?

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

Start Free Scan →Browse All CVEs