Kernel-memory disclosure via stale SCTP association race
Published Jun 24, 2026 · Updated Jun 24, 2026
An out-of-bounds read in SCTP diagnostics in affected Linux Kernel releases allows local users to disclose memory or crash the system. An exact sock_diag lookup can retain an SCTP transport reference while waiting for the socket lock, then format association state after teardown has freed its bind-address list. Exploitation requires local low-privilege access and a successful teardown race; the resulting read can expose unrelated kernel memory or interrupt the system.
Summary
What happened
An out-of-bounds read in SCTP diagnostics in affected Linux Kernel releases allows local users to disclose memory or crash the system. An exact sock_diag lookup can retain an SCTP transport reference while waiting for the socket lock, then format association state after teardown has freed its bind-address list. Exploitation requires local low-privilege access and a successful teardown race; the resulting read can expose unrelated kernel memory or interrupt the system.
The record
- CVE
- CVE-2026-52917
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
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.7
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <480f754580b5686b928977d16a59f20cef83ff01
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <5425de8bd6e9fe5bd67d158e3348171ae7510117
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <5eba3e48d78edd7551b992cb7ba687019b3a78da
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <6657af827e21883ae90693e42e7f59a6aab690b5
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <78c4f964b2f94e405721c093773f6250e1e676b2
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <b2be72d401833194917e44fbd8d8144bb4f2db16
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <e97c2a535e23ed0fdd2660993fb3f10d9535c9bc
- Affected versionversion=8f840e47f190cbe61a96945c13e9551048d42cef <f5af203dec6e0e7a6090fcc2130e9f3901bfc84d
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