CVE-2026-74287
CVE CVE-2026-74287EUVD EUVD-2026-59434Published 2026-08-15T05:57:55.000ZLast changed 2026-08-17T05:45:26.000ZCVSS 9.1
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 2.6.12; patch: 5.15.212; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92e4adfee56f32a963ebb105c6cd9a1ed707262a; patch: 6.18.40; patch: 7.2; patch: 0; patch: 5.10.261; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed8605c6f39b9b84f9a4631db6deb25e7f1e973c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <06c8bf48505f2fef265931db82d5003d302a347b; patch: 6.12.97; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9361d0ca55c4af12aac09e2572852fa91046229; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85f54cf589163a75fa06e37d8c2a4a72824c6dd1; patch: 7.1.5; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <28ba1d3c956604a89168adfb4c97cfc6c509bba5; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a44b2602d57e11e2eb85958d4cd500d14a27d9e; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0; patch: 6.1.178; patch: 6.6.145
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.