CVE-2026-53225

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.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: fix uninit-value in __sctp_rcv_asconf_lookup()

__sctp_rcv_asconf_lookup() in net/sctp/input.c only checks that the ASCONF chunk can hold the ADDIP header and a parameter header, then calls af->from_addr_param(), which reads the full address (16 bytes for IPv6) trusting the parameter's declared length.

An unauthenticated peer can send a truncated trailing ASCONF chunk that declares an IPv6 address parameter but stops after the 4-byte parameter header; reached from the no-association lookup path, from_addr_param() then reads uninitialized bytes past the parameter.

Impact: an unauthenticated SCTP peer makes the receive path read up to 16 bytes of uninitialized memory past a truncated ASCONF address parameter.

The sibling __sctp_rcv_init_lookup() bounds parameters with sctp_walk_params(); this path open-codes the fetch and omits the bound. Verify the whole address parameter lies within the chunk before from_addr_param() reads it, the same class of fix as commit 51e5ad549c43 ("net: sctp: fix KMSAN uninit-value in sctp_inq_pop").

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
40.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (8)

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

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/928dd94db23e8ba340f83d68f7f24d831b7a4426
generic

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e86817b8af4d552f3c6fe04ca52bb0c8c57411d
generic

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ce96f1182644079249a24ac7e2ffc32e0301a46
generic

sctp: fix uninit-value in __sctp_rcv_asconf_lookup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/446e0ecd845abc394b24ae2030a883572bec9d16

Vendor Advisories for CVE-2026-53225(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 10× in last 7d / 245× 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 245 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53225?
CVE-2026-53225 is a critical vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: fix uninit-value in sctprcvasconf_lookup() sctprcvasconf_lookup() in net/sctp/input.c only checks that the ASCONF chunk can hold the ADDIP header and a parameter header, then calls af->fromaddrparam(), which reads the full…
When was CVE-2026-53225 disclosed?
CVE-2026-53225 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53225 actively exploited?
CVE-2026-53225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53225?
CVE-2026-53225 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53225, 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-53225

Explore →

Is Your Infrastructure Affected by CVE-2026-53225?

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