Strix
64.8K

CVE-2026-68376

HIGHCVSS 8.1/10EPSS 0.42%

Last modified

CVE-2026-68376 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 0.42% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
8.1/10

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.42%

35.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1f485649f52929d9937b346a920a522a7363e202, < 317731d01b03c529809df36d3a7d149677a8729d; >= 1f485649f52929d9937b346a920a522a7363e202, < 0528485f27016a42804abe01aa61b39d85fa803e; >= 1f485649f52929d9937b346a920a522a7363e202, < ee5e65964f456adfe14d526fba0bd055de98ecf3; >= 1f485649f52929d9937b346a920a522a7363e202, < 0b4414e43e0861d67276031cc21401d7e87de3da; >= 1f485649f52929d9937b346a920a522a7363e202, < d0a59ba58578e2b330fff80a44fe519f3ba7d8c7; >= 1f485649f52929d9937b346a920a522a7363e202, < a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db; >= 1f485649f52929d9937b346a920a522a7363e202, < 3aa40c3bccac2312ea7cf97f329190637f972b5d; >= 1f485649f52929d9937b346a920a522a7363e202, < e0b5252a59383b77d1b8dbeda00b7184dd95f4d3
LinuxLinux2.6.24

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68376?
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.
How severe is CVE-2026-68376?
CVE-2026-68376 has a CVSS score of 8.1/10 (HIGH severity). The EPSS model estimates a 0.42% probability of exploitation in the next 30 days.
How do I fix CVE-2026-68376?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-68376?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST