Answer in brief
CVE-2026-74287 records a Unknown severity vulnerability in sctp: validate embedded address parameter length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-74287 records a Unknown severity vulnerability in sctp: validate embedded address parameter length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <06c8bf48505f2fef265931db82d5003d302a347b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <28ba1d3c956604a89168adfb4c97cfc6c509bba5 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a44b2602d57e11e2eb85958d4cd500d14a27d9e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85f54cf589163a75fa06e37d8c2a4a72824c6dd1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92e4adfee56f32a963ebb105c6cd9a1ed707262a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed8605c6f39b9b84f9a4631db6deb25e7f1e973c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9361d0ca55c4af12aac09e2572852fa91046229 | 06c8bf48505f2fef265931db82d5003d302a347b, 28ba1d3c956604a89168adfb4c97cfc6c509bba5, 3a44b2602d57e11e2eb85958d4cd500d14a27d9e, 85f54cf589163a75fa06e37d8c2a4a72824c6dd1, 92e4adfee56f32a963ebb105c6cd9a1ed707262a, ed8605c6f39b9b84f9a4631db6deb25e7f1e973c, 0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0, e9361d0ca55c4af12aac09e2572852fa91046229 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <06c8bf48505f2fef265931db82d5003d302a347b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <28ba1d3c956604a89168adfb4c97cfc6c509bba5 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a44b2602d57e11e2eb85958d4cd500d14a27d9e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85f54cf589163a75fa06e37d8c2a4a72824c6dd1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92e4adfee56f32a963ebb105c6cd9a1ed707262a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed8605c6f39b9b84f9a4631db6deb25e7f1e973c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9361d0ca55c4af12aac09e2572852fa91046229 | 06c8bf48505f2fef265931db82d5003d302a347b, 28ba1d3c956604a89168adfb4c97cfc6c509bba5, 3a44b2602d57e11e2eb85958d4cd500d14a27d9e, 85f54cf589163a75fa06e37d8c2a4a72824c6dd1, 92e4adfee56f32a963ebb105c6cd9a1ed707262a, ed8605c6f39b9b84f9a4631db6deb25e7f1e973c, 0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0, e9361d0ca55c4af12aac09e2572852fa91046229 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.