Most recent entries from all

cnvd-2021-17262

2026-10-15T16:50:53.288333+00:00

cnvd-2021-17262

EUVD-2026-25777

2026-10-15T16:50:53.288374+00:00

EUVD-2026-25777

fkie_cve-2021-28032

2026-10-15T16:50:53.288398+00:00

An issue was discovered in the nano_arena crate before 0.5.2 for Rust. There is an aliasing violation in split_at because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or use-after-free.

GHSA-wp34-mqw5-jj85 — Use after free in nano_arena

2026-10-15T16:50:53.288441+00:00

Affected: crates.io: nano_arena

Affected versions of this crate assumed that Borrow was guaranteed to return the same value on .borrow(). The borrowed index value was used to retrieve a mutable reference to a value.

If the Borrow implementation returned a different index, the split arena would allow retrieving the index as a mutable reference creating two mutable references to the same element. This violates Rust's aliasing rules and allows for memory safety issues such as writing out of bounds and use-after-frees.

The flaw was corrected in commit `6b83f9d` by storing the .borrow() value in a temporary variable.

gsd-2021-28032

2026-10-15T16:50:53.288496+00:00

gsd-2021-28032

RUSTSEC-2021-0031 — split_at allows obtaining multiple mutable references to the same data

2026-10-15T16:50:53.288516+00:00

Affected: crates.io: nano_arena

Affected versions of this crate assumed that `Borrow` was guaranteed to return the same value on `.borrow()`. The borrowed index value was used to retrieve a mutable reference to a value.

If the `Borrow` implementation returned a different index, the split arena would allow retrieving the index as a mutable reference creating two mutable references to the same element. This violates Rust's aliasing rules and allows for memory safety issues such as writing out of bounds and use-after-frees.

The flaw was corrected in commit `6b83f9d` by storing the `.borrow()` value in a temporary variable.