Kernel compromise via concurrent SCTP sysctl writes
Published Apr 16, 2025 · Updated Aug 5, 2026
Race condition in the Linux kernel allows local users to crash or compromise the kernel via concurrent writes to an SCTP sysctl. proc_sctp_do_udp_port() fails to serialize sctp_udp_sock_stop() and sctp_udp_sock_start(), allowing two threads to release the same socket and use freed kernel memory. A local user can obtain the required namespace capability through an unprivileged user and network namespace, and the race can cause a kernel panic or control-flow hijack.
Summary
What happened
Race condition in the Linux kernel allows local users to crash or compromise the kernel via concurrent writes to an SCTP sysctl. proc_sctp_do_udp_port() fails to serialize sctp_udp_sock_stop() and sctp_udp_sock_start(), allowing two threads to release the same socket and use freed kernel memory. A local user can obtain the required namespace capability through an unprivileged user and network namespace, and the race can cause a kernel panic or control-flow hijack.
The record
- CVE
- CVE-2025-22062
- Published
- Apr 16, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=046c052b475e7119b6a30e3483e2888fc606a2f8 <10206302af856791fbcc27a33ed3c3eb09b2793d
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <386507cb6fb7cdef598ddcb3f0fa37e6ca9e789d
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <65ccb2793da7401772a3ffe85355c831b313c59f
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <b3598f53211ba1025485306de2733bdd241311a3
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <d3d7675d77622f6ca1aae14c51f80027b36283f8
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <e5178bfc55b3a78000f0f8298e7ade88783ce581
- Affected versionversion=046c052b475e7119b6a30e3483e2888fc606a2f8 <efb8cb487be8f4ba6aaef616011d702d6a083ed1
- Affected versionversion=5.11
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