Answer in brief
CVE-2026-68376 records a Unknown severity vulnerability in sctp: fix auth_hmacs array size in struct sctp_cookie. 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 | >=1f485649f52929d9937b346a920a522a7363e202 <0b4414e43e0861d67276031cc21401d7e87de3da || >=1f485649f52929d9937b346a920a522a7363e202 <d0a59ba58578e2b330fff80a44fe519f3ba7d8c7 || >=1f485649f52929d9937b346a920a522a7363e202 <a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db || >=1f485649f52929d9937b346a920a522a7363e202 <3aa40c3bccac2312ea7cf97f329190637f972b5d || >=1f485649f52929d9937b346a920a522a7363e202 <e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 | 0b4414e43e0861d67276031cc21401d7e87de3da, d0a59ba58578e2b330fff80a44fe519f3ba7d8c7, a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db, 3aa40c3bccac2312ea7cf97f329190637f972b5d, e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 |
| Linux/Linuxgeneric | 2.6.24 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68376 records a Unknown severity vulnerability in sctp: fix auth_hmacs array size in struct sctp_cookie. 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 | >=1f485649f52929d9937b346a920a522a7363e202 <0b4414e43e0861d67276031cc21401d7e87de3da || >=1f485649f52929d9937b346a920a522a7363e202 <d0a59ba58578e2b330fff80a44fe519f3ba7d8c7 || >=1f485649f52929d9937b346a920a522a7363e202 <a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db || >=1f485649f52929d9937b346a920a522a7363e202 <3aa40c3bccac2312ea7cf97f329190637f972b5d || >=1f485649f52929d9937b346a920a522a7363e202 <e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 | 0b4414e43e0861d67276031cc21401d7e87de3da, d0a59ba58578e2b330fff80a44fe519f3ba7d8c7, a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db, 3aa40c3bccac2312ea7cf97f329190637f972b5d, e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 |
| Linux/Linuxgeneric | 2.6.24 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.