Review reviewCritical

CVE-2026-52924

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

In the Linux kernel, the following vulnerability has been resolved: sctp: purge outqueue on stale COOKIE-ECHO handling sctp_stream_update() is only invoked when the association is moved into COOKIE_WAIT during association setup/reconfiguration. In this path, the outbound stream scheduler state (stream->out_curr) is expected to be clean, since no user data should have been transmitted yet unless the state machine has already partially progressed. However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a Stale Cookie ERROR is received, the association is rolled back from COOKIE_ECHOED...

CVSS
9.8
EPSS
0.33%
25.6% percentile
CISA KEV
Not listed
Published
2026.06.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.33%
Technical severityCVSS 9.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: sctp: purge outqueue on stale COOKIE-ECHO handling sctp_stream_update() is only invoked when the association is moved into COOKIE_WAIT during association setup/reconfiguration. In this path, the outbound stream scheduler state (stream->out_curr) is expected to be clean, since no user data should have been transmitted yet unless the state machine has already partially progressed. However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a Stale Cookie ERROR is received, the association is rolled back from COOKIE_ECHOED...

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6
Affected versions
>= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < 84b7a319105db2f917ccdcf502bdc866082b1285, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < f46e1d1a758878f0d22c4fbbd1bf42bb7165d1e8, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < 3c0741a441a7df7099d7ca6a64a6a0de09c677c8, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < 2afc9e684dc7fecf73db1edc937ebbc47b4b68dc, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < 1d4652f677906a64487c13f9ace54b0eb263b5d0, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < a6207349e703cfc04756a4d16dec9176135813a5, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < 83ade59e5da365f4bf8bce72c5a38774202b442f, >= 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 < e374b22e9b07b72a25909621464ff74096151bfb, >= 4.15, >= 4.15 < 5.10.259, >= 5.11 < 5.15.210, >= 5.16 < 6.1.176, >= 6.2 < 6.6.143, >= 6.7 < 6.12.94, >= 6.13 < 6.18.36, >= 6.19 < 7.0.13, 7.1
Fixed versions
5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416, CWE-825