CVE-2026-80890

sctp: reject stale cookies with mismatched verification tags

N/A
Published: September 4, 2026 at 05:11 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: reject stale cookies with mismatched verification tags sctp_unpack_cookie() skips cookie expiration checks whenever an association already exists. This is broader than the exception in RFC 9260 Section 5.2.4. For an existing association, Section 5.2.4 permits an expired State Cookie only when both Verification Tags in the cookie match the current association. Otherwise, the packet SHOULD be discarded and a Stale Cookie ERROR MUST be sent. The broad check lets an expired Action A restart cookie reach sctp_sf_do_dupcook_a(). In a runtime test with the default 60 second cookie lifetime, replaying such a cookie after 65 seconds returned a COOKIE-ACK and restarted the association. Check cookie expiration unless both Verification Tags match. This preserves the Action D exception for a lost COOKIE ACK while rejecting expired cookies in all other cases.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2652.6.12 ≤ v < 5.15.2162.6.12 ≤ v < 6.1.1832.6.12 ≤ v < 6.12.1032.6.12 ≤ v < 6.18.442.6.12 ≤ v < 6.6.1512.6.12 ≤ v < 7.1.82.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 35c279113498d19a8734e2aae67b951b9b20f634 (fixed)
Vendor states this is fixed in 61baa5020b0afb41bfd97f8f6ce5e336c4a4546e (fixed)
Vendor states this is fixed in 817cffdbdbdf50e1f2b016599d1897de3ca54964 (fixed)
Vendor states this is fixed in 9d8da8e0a9bce4a340af60dd0446bc7eb8d07587 (fixed)
Vendor states this is fixed in a0d1693923f41d6f49083aa2446686aed09d1d79 (fixed)
Vendor states this is fixed in c151daba0ceb1fb068a215b07de89fb1eb5f87bc (fixed)
Vendor states this is fixed in c68557a49e960dbcdede22c7a9b488603078b8b4 (fixed)
Vendor states this is fixed in f6e3cc296372accad4ee57405195021231ef4bcb (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card