Remote kernel crash via stale SCTP scheduler pointer
Published Jun 24, 2026 · Updated Jun 24, 2026
Use-after-free in the Linux Kernel SCTP state machine allows remote attackers to crash the kernel via a crafted Stale Cookie Error. During rollback from COOKIE_ECHOED to COOKIE_WAIT, sctp_stream_update() frees the old stream table but leaves stream->out_curr referencing a released sctp_stream_out entry used by later scheduler dequeues. A remote SCTP peer needs no host account but must reach the stale-cookie rollback after user data is queued; the demonstrated consequence is a kernel crash.
Summary
What happened
Use-after-free in the Linux Kernel SCTP state machine allows remote attackers to crash the kernel via a crafted Stale Cookie Error. During rollback from COOKIE_ECHOED to COOKIE_WAIT, sctp_stream_update() frees the old stream table but leaves stream->out_curr referencing a released sctp_stream_out entry used by later scheduler dequeues. A remote SCTP peer needs no host account but must reach the stale-cookie rollback after user data is queued; the demonstrated consequence is a kernel crash.
The record
- CVE
- CVE-2026-52924
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-825, CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.15
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <1d4652f677906a64487c13f9ace54b0eb263b5d0
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <2afc9e684dc7fecf73db1edc937ebbc47b4b68dc
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <3c0741a441a7df7099d7ca6a64a6a0de09c677c8
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <83ade59e5da365f4bf8bce72c5a38774202b442f
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <84b7a319105db2f917ccdcf502bdc866082b1285
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <a6207349e703cfc04756a4d16dec9176135813a5
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <e374b22e9b07b72a25909621464ff74096151bfb
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <f46e1d1a758878f0d22c4fbbd1bf42bb7165d1e8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo