CVE-2026-52917

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — Patch released this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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(5)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-31.31~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.el8_102026-09-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-52917?
CVE-2026-52917 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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