An issue was discovered in the futures-task crate before 0.3.6 for Rust. futures_task::waker may cause a use-after-free in a non-static type situation.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Futures-task | Rust-lang | 0.2.1 (including) | 0.3.6 (excluding) |
| Rust-futures-task | Ubuntu | hirsute | * |
| Rust-futures-task | Ubuntu | impish | * |
| Rust-futures-task | Ubuntu | kinetic | * |
| Rust-futures-task | Ubuntu | lunar | * |
| Rust-futures-task | Ubuntu | mantic | * |
| Rust-futures-task | Ubuntu | oracular | * |
| Rust-futures-task | Ubuntu | plucky | * |
| Rust-futures-task | Ubuntu | trusty | * |