CVE-2026-53224

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

sctp: validate embedded INIT chunk and address list lengths in cookie

sctp_unpack_cookie() only checked that the embedded INIT chunk length did not exceed the remaining cookie payload, but did not ensure that the INIT chunk is large enough to contain a complete INIT header.

A malformed COOKIE_ECHO can therefore carry a truncated INIT chunk whose length field is smaller than sizeof(struct sctp_init_chunk). Later, sctp_process_init() accesses INIT parameters unconditionally, which may lead to out-of-bounds reads.

In addition, raw_addr_list_len is not fully validated against the remaining cookie payload. When cookie authentication is disabled, an attacker can supply an oversized raw_addr_list_len and cause sctp_raw_to_bind_addrs() to read beyond the end of the cookie. The address parser also lacks sufficient bounds checks for parameter headers and lengths, allowing malformed address parameters to trigger out-of-bounds reads.

Fix this by:

  • requiring the embedded INIT chunk length to be at least sizeof(struct
sctp_init_chunk);
  • validating that the INIT chunk and raw address list together fit
within the cookie payload;
  • verifying sufficient data exists for each address parameter header and
payload before parsing it.

Note that sctp_verify_init() must be called after sctp_unpack_cookie() and before sctp_process_init() when cookie authentication is disabled. This will be addressed in a separate patch.

CVSS v3
9.1
EG Score
9.1(medium)
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 PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

sctp: validate embedded INIT chunk and address list lengths in cookie - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f4c80a2a7e6d06753b89a578b710a2499a5e62b
generic

sctp: validate embedded INIT chunk and address list lengths in cookie - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/512a9bb77c04ac9927648ea58af617e472be96e6
generic

sctp: validate embedded INIT chunk and address list lengths in cookie - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7560afb8cddafd829e709d7ea09230e45a825557

Vendor Advisories for CVE-2026-53224(1)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-29.29) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1010.10) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1010.10~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1035.36) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.257.241) @ bionic2026-08-30ubuntu
ubuntulinux-tools-oracle (4.15.0.1158.169~16.04.1) @ xenial2026-08-30ubuntu
ubuntulinux-virtual (3.13.0.217.227) @ trusty2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-29.29~24.04.2) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-138.138~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-138.138.1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1077 (5.15.0-1077.81) @ jammy2026-08-30ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1005.6) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1061.64.1) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.190.200~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-gke (4.15.0.1189.206~16.04.1) @ xenial2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.190.157) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1064.71~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1055.57) @ jammy2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2052.54) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1206.221~16.04.1) @ xenial2026-08-30ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1119.128~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1110.109) @ jammy2026-08-30ubuntu
ubuntulinux-tools-ibm-5.15 (5.15.0.1108.105) @ jammy2026-08-30ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
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.

All Vendor Advisories

(25)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-53224?
CVE-2026-53224 is a critical vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded INIT chunk and address list lengths in cookie sctpunpackcookie() only checked that the embedded INIT chunk length did not exceed the remaining cookie payload, but did not ensure that the INIT chunk is large…
When was CVE-2026-53224 disclosed?
CVE-2026-53224 was first published in the National Vulnerability Database on June 25, 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-53224 actively exploited?
CVE-2026-53224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53224?
CVE-2026-53224 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53224, 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-53224

Explore →

Is Your Infrastructure Affected by CVE-2026-53224?

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