CVE-2026-52917

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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: diag: reject stale associations in dump_one path

The SCTP exact sock_diag lookup can hold a transport reference, block on lock_sock(sk), and then resume after sctp_association_free() has marked the association dead and freed its bind address list.

When that happens, inet_assoc_attr_size() and inet_diag_msg_sctpasoc_fill() can still dereference association state that is no longer valid for reporting. In particular, inet_diag_msg_sctpasoc_fill() may read an empty bind-address list as a real sctp_sockaddr_entry and trigger an out-of-bounds read from unrelated association memory.

Reject the association after taking the socket lock if it has been reaped or detached from the endpoint, and report the lookup as stale. This keeps the exact dump-one path from formatting torn association state.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
2.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

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

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78c4f964b2f94e405721c093773f6250e1e676b2
generic

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6657af827e21883ae90693e42e7f59a6aab690b5
generic

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5eba3e48d78edd7551b992cb7ba687019b3a78da
generic

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5425de8bd6e9fe5bd67d158e3348171ae7510117
generic

sctp: diag: reject stale associations in dump_one path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/480f754580b5686b928977d16a59f20cef83ff01

Vendor Advisories for CVE-2026-52917(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 46× in last 7d / 59× 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 22:19 UTCEG score recompute
  2. 2026-07-06 22:19 UTCVendor advisory
  3. 2026-07-06 22:19 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 10:00 UTCEG score recompute
  7. 2026-07-06 10:00 UTCVendor advisory
  8. 2026-07-06 10:00 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 21:42 UTCEG score recompute
  12. 2026-07-05 21:42 UTCVendor advisory
  13. 2026-07-05 21:42 UTCGHSA enrichment
  14. 2026-07-05 09:29 UTCEG score recompute
  15. 2026-07-05 09:29 UTCVendor advisory
  16. 2026-07-05 09:29 UTCGHSA enrichment
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 21:16 UTCEG score recompute
  19. 2026-07-04 21:16 UTCVendor advisory
  20. 2026-07-04 21:15 UTCGHSA enrichment
  21. 2026-07-04 09:01 UTCEG score recompute
  22. 2026-07-04 09:01 UTCVendor advisory
  23. 2026-07-04 09:01 UTCGHSA enrichment
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 20:47 UTCEG score recompute
Show 34 more
  1. 2026-07-03 20:47 UTCVendor advisory
  2. 2026-07-03 20:47 UTCGHSA enrichment
  3. 2026-07-03 08:34 UTCEG score recompute
  4. 2026-07-03 08:34 UTCVendor advisory
  5. 2026-07-03 08:34 UTCGHSA enrichment
  6. 2026-07-02 20:19 UTCEG score recompute
  7. 2026-07-02 20:19 UTCVendor advisory
  8. 2026-07-02 20:19 UTCGHSA enrichment
  9. 2026-07-02 08:06 UTCEG score recompute
  10. 2026-07-02 08:06 UTCVendor advisory
  11. 2026-07-02 08:06 UTCGHSA enrichment
  12. 2026-07-01 19:51 UTCEG score recompute
  13. 2026-07-01 19:51 UTCVendor advisory
  14. 2026-07-01 19:51 UTCGHSA enrichment
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 07:39 UTCEG score recompute
  17. 2026-07-01 07:39 UTCVendor advisory
  18. 2026-07-01 07:39 UTCGHSA enrichment
  19. 2026-06-30 19:26 UTCEG score recompute▲ 7.10
  20. 2026-06-30 19:26 UTCVendor advisory
  21. 2026-06-30 19:26 UTCGHSA enrichment
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  26. 2026-06-28 04:56 UTCEPSS rescore
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-27 14:04 UTCEG score recompute
  29. 2026-06-27 14:04 UTCGHSA enrichment
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-24 14:05 UTCEPSS rescore
  33. 2026-06-24 08:42 UTCEG score recompute
  34. 2026-06-24 08:40 UTCNVD updatefirst tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-52917?
CVE-2026-52917 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: diag: reject stale associations in dump_one path The SCTP exact sock_diag lookup can hold a transport reference, block on locksock(sk), and then resume after sctpassociation_free() has marked the association dead and freed…
When was CVE-2026-52917 disclosed?
CVE-2026-52917 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-52917 actively exploited?
CVE-2026-52917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52917?
CVE-2026-52917 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-52917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52917, 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-52917

Explore →

Is Your Infrastructure Affected by CVE-2026-52917?

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

Start Free Scan →Browse All CVEs