Memory corruption via unchecked heap size metadata writes
Published Sep 7, 2022 · Updated Apr 22, 2025
Out-of-bounds writes in Rust OSDev linked-list-allocator before 0.10.2 allow local users to corrupt memory through unsafe heap APIs. Heap initialization writes free-list metadata without rejecting undersized regions, while Heap::extend rounds up short growth and can write at address zero. Exploitation requires a consuming program to pass unsafe initialization or extension inputs; consequences include memory corruption or a service crash.
Summary
What happened
Out-of-bounds writes in Rust OSDev linked-list-allocator before 0.10.2 allow local users to corrupt memory through unsafe heap APIs. Heap initialization writes free-list metadata without rejecting undersized regions, while Heap::extend rounds up short growth and can write at address zero. Exploitation requires a consuming program to pass unsafe initialization or extension inputs; consequences include memory corruption or a service crash.
The record
- CVE
- CVE-2022-36086
- Published
- Sep 7, 2022
- Updated
- Apr 22, 2025
- Vendor
- Rust OSDev
- Product
- linked-list-allocator
- Classifications
- CWE-119, CWE-1284
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=< 0.10.2
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