linked_list_allocator vulnerable to out-of-bound writes on `Heap` initialization and `Heap::extend`
linked_list_allocator is an allocator usable for no_std systems. Prior to version 0.10.2, the heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than `3 * size_of::` because of metadata write operations. This vulnerability impacts all the initialization functions on the `Heap` and `LockedHeap` types, including `Heap::new`, `Heap::init`, `Heap::init_from_slice`, and `LockedHeap::new`. It also affects multiple uses of the `Heap::extend` method. Version 0.10.2 contains a patch for the issue. As a workaround, ensure that the heap is only initialized with a size larger than `3 * size_of::` and that the `Heap::extend` method is only called with sizes larger than `2 * size_of::()`. Also, ensure that the total heap size is (and stays) a multiple of `2 * size_of::()`.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-36086
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:21 UTC · Revision 1
Source evidence
linked_list_allocator vulnerable to out-of-bound writes on `Heap` initialization and `Heap::extend`
core-osv · Original sourcePublished 7 Sept 2022, 22:50 UTC
linked_list_allocator is an allocator usable for no_std systems. Prior to version 0.10.2, the heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than `3 * size_of::` because of metadata write operations. This vulnerability impacts all the initialization functions on the `Heap` and `LockedHeap` types, including `Heap::new`, `Heap::init`, `Heap::init_from_slice`, and `LockedHeap::new`. It also affects multiple uses of the `Heap::extend` method. Version 0.10.2 contains a patch for the issue. As a workaround, ensure that the heap is only initialized with a size larger than `3 * size_of::` and that the `Heap::extend` method is only called with sizes larger than `2 * size_of::()`. Also, ensure that the total heap size is (and stays) a multiple of `2 * size_of::()`.
osv:CVE-2022-36086
Complete source record
{
"id": "f646d5a96d66fd74aceae0ed18f0053eb772df6fef646401d9893754947f95bf",
"url": "https://osv.dev/vulnerability/CVE-2022-36086",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "linked_list_allocator vulnerable to out-of-bound writes on `Heap` initialization and `Heap::extend`",
"summary": "linked_list_allocator is an allocator usable for no_std systems. Prior to version 0.10.2, the heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than `3 * size_of::` because of metadata write operations. This vulnerability impacts all the initialization functions on the `Heap` and `LockedHeap` types, including `Heap::new`, `Heap::init`, `Heap::init_from_slice`, and `LockedHeap::new`. It also affects multiple uses of the `Heap::extend` method. Version 0.10.2 contains a patch for the issue. As a workaround, ensure that the heap is only initialized with a size larger than `3 * size_of::` and that the `Heap::extend` method is only called with sizes larger than `2 * size_of::()`. Also, ensure that the total heap size is (and stays) a multiple of `2 * size_of::()`.",
"evidence": "osv:CVE-2022-36086",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2022-36086",
"aliases": [
"CVE-2022-36086",
"GHSA-xg8p-34w2-j49j",
"RUSTSEC-2022-0063"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/rust-osdev/linked-list-allocator",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "5eb2bc6e671e15f3953e74e7b108cf59e724c2a0"
},
{
"fixed": "013b0758643943e8df5b17bbb495460ff47e8bbf"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:rust-osdev:linked-list-allocator:*:*:*:*:*:rust:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.10.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "013b0758643943e8df5b17bbb495460ff47e8bbf"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v0.10.1",
"v0.10.0",
"v0.9.1",
"v0.9.0",
"v0.8.11",
"v0.8.10",
"v0.8.9",
"v0.8.8",
"v0.8.7",
"v0.8.6",
"v0.8.5",
"v0.8.4",
"v0.8.3",
"v0.8.2",
"v0.8.1",
"v0.8.0",
"v0.7.0",
"v0.6.6",
"v0.6.5",
"v0.6.4",
"v0.6.3",
"v0.6.2",
"v0.6.1",
"v0.6.0",
"v0.5.0",
"v0.4.3",
"v0.4.2",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.2.7",
"v0.2.6",
"v0.2.5",
"v0.2.4",
"linked_list_allocator-0.2.3",
"v0.2.1",
"v0.2.0",
"v0.1.3",
"v0.1.2",
"v0.1.1",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-36086.json"
}
}
],
"modified": "2026-10-28T02:30:40.349048102Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/36xxx/CVE-2022-36086.json",
"https://github.com/rust-osdev/linked-list-allocator/security/advisories/GHSA-xg8p-34w2-j49j",
"https://nvd.nist.gov/vuln/detail/CVE-2022-36086",
"https://github.com/rust-osdev/linked-list-allocator/commit/013b0758643943e8df5b17bbb495460ff47e8bbf"
],
"provider_metadata": {
"cwe_ids": [
"CWE-119",
"CWE-787"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/36xxx/CVE-2022-36086.json"
}
},
"related_cves": [
{
"value": "CVE-2022-36086",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507951,
"published_at": "2022-09-07T22:50:09+00:00"
}