Use-after-free when a future's `Drop` panics while the container is dropped
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · RUSTSEC-2026-0298
Published`Storage::clear` walks the slab, empties each entry and frees the `Task` allocation once its reference count reaches zero. `self.tasks.set_len(0)` only runs after the loop. Emptying an entry drops the user future it holds, and `T` carries no bounds excluding a panicking `Drop`. If one unwinds, the length is never committed and `self.tasks` still holds the pointers already processed. `Drop for Storage` calls `clear` again, and the second pass dereferences `(*task.as_ptr()).entry` on allocations the first pass already freed — a use-after-free (CWE-416) reachable from safe Rust. `Storage` is reached only through `Unordered`, whose `Drop` calls `clear`. No particular method call is needed; dropping the container is enough. ## Mitigation Update to 0.10.3.
- Source published
- 12 Sep 2026 12:00:00 UTC
- Source modified
- 22 Sep 2026 07:45:03 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.