CVE-2026-68376
CVE CVE-2026-68376EUVD EUVD-2026-55562Published 2026-08-10T12:03:54.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: sctp: fix auth_hmacs array size in struct sctp_cookie The auth_hmacs array in struct sctp_cookie is supposed to store a complete SCTP_AUTH_HMAC_ALGO parameter, which consists of a struct sctp_paramhdr followed by N HMAC identifiers. However, the array size was calculated using an extra 2 bytes instead of sizeof(struct sctp_paramhdr), which is 4 bytes. When four HMAC identifiers are configured, the HMAC-ALGO parameter stored in the endpoint is larger than the auth_hmacs buffer in the cookie. As a result, sctp_association_init() copies beyond the end of auth_hmacs when initializing the association, corrupting the adjacent auth_chunks field. This can lead to an invalid HMAC identifier being accepted and later cause an out-of-bounds read in sctp_auth_get_hmac(). Fix the array size calculation by including the full SCTP parameter header size.
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 patch: 6.6.148; 1f485649f52929d9937b346a920a522a7363e202 <3aa40c3bccac2312ea7cf97f329190637f972b5d; 2.6.24; patch: 0; patch: 6.18.42; 1f485649f52929d9937b346a920a522a7363e202 <e0b5252a59383b77d1b8dbeda00b7184dd95f4d3; patch: 6.12.101; patch: 7.2-rc4; 1f485649f52929d9937b346a920a522a7363e202 <0b4414e43e0861d67276031cc21401d7e87de3da; patch: 7.1.6; 1f485649f52929d9937b346a920a522a7363e202 <d0a59ba58578e2b330fff80a44fe519f3ba7d8c7; 1f485649f52929d9937b346a920a522a7363e202 <a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db
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.