Linux
sctp: fix auth_hmacs array size in struct sctp_cookie
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1f485649f52929d9937b346a920a522a7363e202, < 317731d01b03c529809df36d3a7d149677a8729d
- >= 1f485649f52929d9937b346a920a522a7363e202, < 0528485f27016a42804abe01aa61b39d85fa803e
- >= 1f485649f52929d9937b346a920a522a7363e202, < ee5e65964f456adfe14d526fba0bd055de98ecf3
- >= 1f485649f52929d9937b346a920a522a7363e202, < 0b4414e43e0861d67276031cc21401d7e87de3da
- >= 1f485649f52929d9937b346a920a522a7363e202, < d0a59ba58578e2b330fff80a44fe519f3ba7d8c7
- >= 1f485649f52929d9937b346a920a522a7363e202, < a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db
- >= 1f485649f52929d9937b346a920a522a7363e202, < 3aa40c3bccac2312ea7cf97f329190637f972b5d
- >= 1f485649f52929d9937b346a920a522a7363e202, < e0b5252a59383b77d1b8dbeda00b7184dd95f4d3
Fixed in 317731d01b03c529809df36d3a7d149677a8729d, 0528485f27016a42804abe01aa61b39d85fa803e, ee5e65964f456adfe14d526fba0bd055de98ecf3, 0b4414e43e0861d67276031cc21401d7e87de3da, d0a59ba58578e2b330fff80a44fe519f3ba7d8c7, a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db, 3aa40c3bccac2312ea7cf97f329190637f972b5d, e0b5252a59383b77d1b8dbeda00b7184dd95f4d3
- 2.6.24
Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.6, 7.2
Mitigation
Upgrade Linux to 317731d01b03c529809df36d3a7d149677a8729d or 0528485f27016a42804abe01aa61b39d85fa803e or ee5e65964f456adfe14d526fba0bd055de98ecf3 or 0b4414e43e0861d67276031cc21401d7e87de3da or d0a59ba58578e2b330fff80a44fe519f3ba7d8c7 or a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db or 3aa40c3bccac2312ea7cf97f329190637f972b5d or e0b5252a59383b77d1b8dbeda00b7184dd95f4d3 or later.
Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.148 or 6.12.101 or 6.18.42 or 7.1.6 or 7.2 or later.
Timeline
Days relative to CVE publicationFirst public PoC 43 days after publication; not in CISA KEV. First PoC: gagaltotal/CVE-2026-68376-Ubuntu-7.0.0-30-Poc (created 22 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| gagaltotal/CVE-2026-68376-Ubuntu-7.0.0-30-Poc | 22 Sep 2026 +43 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.