Kernel memory corruption via SCTP diagnostic race
Published Dec 9, 2025 · Updated Aug 5, 2026
Out-of-bounds write in Linux kernel SCTP diagnostics from 4.7 allows local users to corrupt kernel memory through a concurrent address-list change. The unlocked sctp_diag_dump path allocates output space from one address-list size, then sctp_ep_dump writes a larger list after that list grows. Low-privileged local access and a successful race are required; the directly established consequence is kernel memory corruption.
Summary
What happened
Out-of-bounds write in Linux kernel SCTP diagnostics from 4.7 allows local users to corrupt kernel memory through a concurrent address-list change. The unlocked sctp_diag_dump path allocates output space from one address-list size, then sctp_ep_dump writes a larger list after that list grows. Low-privileged local access and a successful race are required; the directly established consequence is kernel memory corruption.
The record
- CVE
- CVE-2025-40331
- Published
- Dec 9, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 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=4.7
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <2fe08fcaacb7eb019fa9c81db39b2214de216677
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <3006959371007fc2eae4a078f823c680fa52de1a
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <584307275b2048991b2e8984962189b6cc0a9b85
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <72e3fea68eac8d088e44c3dd954e843478e9240e
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <89eac1e150dbd42963e13d23828cb8c4e0763196
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <95aef86ab231f047bb8085c70666059b58f53c09
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <b106a68df0650b694b254427cd9250c04500edd3
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <c9119f243d9c0da3c3b5f577a328de3e7ffd1b42
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
No sourced classifications are available.
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