Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Remote unauthenticated malformed SCTP packet triggers an out-of-bounds read with no interaction, causing memory disclosure (C:H) and crash/DoS (A:H); no integrity impact and no scope change.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Linux
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Lifecycle Timeline
5DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
sctp: validate embedded address parameter length
sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer parameter is large enough to contain an embedded address parameter header, but does not verify that the embedded address parameter's declared length fits within the bounds of the outer parameter.
Later, sctp_process_param() and sctp_process_asconf_param() extract the embedded address parameter and pass it to af->from_addr_param(), which uses the address parameter length to parse the variable-length address payload. A malformed peer can therefore advertise an embedded address parameter length that exceeds the remaining bytes in the enclosing parameter.
Validate that addr_param->p.length does not exceed the space available after the sctp_addip_param header before processing the embedded address parameter. Reject malformed parameters when the embedded address length extends beyond the enclosing parameter bounds.
This prevents out-of-bounds reads when parsing malformed parameters carried in INIT or ASCONF processing paths.
AnalysisAI
Out-of-bounds read in the Linux kernel's SCTP protocol implementation allows a malicious SCTP peer to trigger memory over-reads during INIT or ASCONF chunk processing. The flaw stems from insufficient validation of an embedded address parameter's declared length inside ADD_IP, DEL_IP, and SET_PRIMARY ASCONF parameters, letting a crafted peer advertise a length exceeding the enclosing parameter's bounds. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the target has the kernel SCTP module loaded and is reachable via SCTP (IP protocol 132) - the malformed ADD_IP, DEL_IP, or SET_PRIMARY ASCONF parameter must be delivered inside an INIT or ASCONF chunk that the SCTP stack will parse, which can occur during association setup. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals conflict in a way worth stating plainly: the CVSS vector (AV:N/AC:L/PR:N/UI:N, C:H/A:H) yields 9.1 CRITICAL implying trivial remote unauthenticated compromise, yet EPSS is only 0.18% (7th percentile) and there is no KEV listing and no known POC, indicating low real-world exploitation likelihood. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker able to send SCTP traffic to a target host crafts an INIT or ASCONF chunk containing an ADD_IP/DEL_IP/SET_PRIMARY parameter whose embedded address parameter declares a length longer than the enclosing parameter, causing the kernel to read beyond the buffer while parsing the address payload. This yields a kernel memory over-read that can leak adjacent memory contents or crash the host (DoS). … |
| Remediation | Vendor-released patch: upgrade to a fixed stable kernel for your branch - 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, or 7.1.5 (7.2-rc1 for mainline) or later, as published at git.kernel.org (e.g. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit which Linux systems have SCTP protocol support enabled by checking kernel module status and network configurations to prioritize patching scope. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Buffer Overflow
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-59434
GHSA-gffv-4hwx-62gg