Local system crash via SCTP use-after-free
Published Apr 20, 2023 · Updated Mar 18, 2025
NULL pointer dereference in Linux Kernel before 5.19 allows local users to crash the system through a failed SCTP stream allocation. In sctp_stream_init, failed stream_in allocation frees stream_out while queued client data still refers to it, and later teardown dereferences it. Low-privileged local access is required to send SCTP data before connecting, and successful triggering interrupts the entire host without exposing or changing data.
Summary
What happened
NULL pointer dereference in Linux Kernel before 5.19 allows local users to crash the system through a failed SCTP stream allocation. In sctp_stream_init, failed stream_in allocation frees stream_out while queued client data still refers to it, and later teardown dereferences it. Low-privileged local access is required to send SCTP data before connecting, and successful triggering interrupts the entire host without exposing or changing data.
The record
- CVE
- CVE-2023-2177
- Published
- Apr 20, 2023
- Updated
- Mar 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record 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=Linux Kernel prior to Kernel 5.19 RC17
What conditions does exploitation require?
What is affected?
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.
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