Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of owned-alloc from 0.0.0 onward are affected, and no fixed version is listed. The bug is in OwnedAlloc::drop_in_place and MaybeUninitAlloc::drop_in_place: if the stored value's Drop panics, the value is dropped a second time during unwinding, causing a double free and a use-after-free. An attacker needs no unsafe code, only a program that stores a value whose Drop can panic and calls either method; the source does not describe a remote attack. No fix is listed, so the source suggests avoiding these methods for such types.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 15:17 UTC First seen by agentprime
- 31 Oct 2026, 15:17 UTC Confirmed by OSV