CVE-2026-53224: sctp: validate embedded INIT chunk and address list lengths in cookie
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 29ab56e7660b6f849c10c46e87e085649df751eb, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b.
Low priority for now. Upgrade to Linux Linux 29ab56e7660b6f849c10c46e87e085649df751eb, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- SUSE-SU-2026:23257-1
- SUSE-SU-2026:23258-1
- SUSE-SU-2026:23259-1
- SUSE-SU-2026:23260-1
- SUSE-SU-2026:23261-1
- SUSE-SU-2026:23262-1
- SUSE-SU-2026:23263-1
- SUSE-SU-2026:23264-1
- SUSE-SU-2026:23265-1
- SUSE-SU-2026:23266-1
- SUSE-SU-2026:23267-1
- SUSE-SU-2026:23268-1
- SUSE-SU-2026:23269-1
- SUSE-SU-2026:23270-1
- SUSE-SU-2026:23271-1
- SUSE-SU-2026:23272-1
- SUSE-SU-2026:23279-1
- SUSE-SU-2026:23280-1
- SUSE-SU-2026:23281-1
- SUSE-SU-2026:23282-1
- Published
- Jun 25, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-125
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.12.1 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel2.6.12
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dd75066882ecc4ec8df3f5384b4b9fa9579be8f0affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 29ab56e7660b6f849c10c46e87e085649df751ebaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7560afb8cddafd829e709d7ea09230e45a825557affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 512a9bb77c04ac9927648ea58af617e472be96e6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6f4c80a2a7e6d06753b89a578b710a2499a5e62baffected · git
- before 2.6.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_71 | before 17-2.1 | 17-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_72 | before 16-2.1 | 16-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_75 | before 12-2.1 | 12-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_76 | before 12-2.1 | 12-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_79 | before 8-2.1 | 8-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_83 | before 5-2.1 | 5-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_84 | before 3-2.1 | 3-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_85 | before 2-2.1 | 2-2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_42 | before 22-150400.2.1 | 22-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_43 | before 19-150400.2.1 | 19-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_45 | before 16-150400.2.1 | 16-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_46 | before 12-150400.2.1 | 12-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_48 | before 10-150400.2.1 | 10-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_49 | before 8-150400.2.1 | 8-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_50 | before 8-150400.2.1 | 8-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_52 | before 6-150400.2.1 | 6-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_53 | before 5-150400.2.1 | 5-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_54 | before 4-150400.2.1 | 4-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_55 | before 4-150400.2.1 | 4-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_56 | before 4-150400.2.1 | 4-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_57 | before 2-150400.2.1 | 2-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_29 | before 20-150500.2.1 | 20-150500.2.1 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53222Jun 25, 2026 · ptp: ocp: fix resource freeing order22Monitor
- ← EarlierCVE-2026-53223Jun 25, 2026 · net: guard timestamp cmsgs to real error queue skbs28Monitor
- Later →CVE-2026-53225Jun 25, 2026 · sctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 29ab56e7660b6f849c10c46e87e085649df751eb | Vendor (CNA) |
| Linux Linux | 512a9bb77c04ac9927648ea58af617e472be96e6 | Vendor (CNA) |
| Linux Linux | 6f4c80a2a7e6d06753b89a578b710a2499a5e62b | Vendor (CNA) |
| Linux Linux | 7560afb8cddafd829e709d7ea09230e45a825557 | Vendor (CNA) |
| Linux Linux | b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0 | Vendor (CNA) |
| Linux Linux | dd75066882ecc4ec8df3f5384b4b9fa9579be8f0 | Vendor (CNA) |
| debian:linux | 7.0.13-1 · Debian:14 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_10 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_11 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_12 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_13 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_14 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_15 | 2-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_4 | 11-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_5 | 10-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_6 | 9-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_7 | 8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_8 | 7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_9 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/512a9bb77c04ac9927648ea58af617e472be96e6
- git.kernel.org/stable/c/6f4c80a2a7e6d06753b89a578b710a2499a5e62b
- git.kernel.org/stable/c/7560afb8cddafd829e709d7ea09230e45a825557
- git.kernel.org/stable/c/b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0
- git.kernel.org/stable/c/dd75066882ecc4ec8df3f5384b4b9fa9579be8f0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.