Local kernel crash via stale SCTP out_curr pointer
Published May 1, 2025 · Updated May 11, 2026
SCTP scheduling in Linux 4.15 through 6.1-rc4 allows local users to crash the kernel while sending a partially reliable message. sctp_prsctp_prune_unsent() removes the final fragment without calling sctp_sched_dequeue_done(), leaving out_curr aimed at an empty queue. A low-privileged local user must exercise SCTP message sending; the resulting list corruption interrupts the host without reported data disclosure or modification.
Summary
What happened
SCTP scheduling in Linux 4.15 through 6.1-rc4 allows local users to crash the kernel while sending a partially reliable message. sctp_prsctp_prune_unsent() removes the final fragment without calling sctp_sched_dequeue_done(), leaving out_curr aimed at an empty queue. A low-privileged local user must exercise SCTP message sending; the resulting list corruption interrupts the host without reported data disclosure or modification.
The record
- CVE
- CVE-2022-49838
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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 <2ea600b598dd3e061854dd4dd5b4c815397dfcea
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <2f201ae14ae0f91dbf1cffea7bb1e29e81d4d108
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <3eff34e01062ec08fbb45ce2baaaa644550be821
- Affected versionversion=5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 <e27458b18b35caee4b27b37a4a9c503b93cae5cc
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.
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