github-actions[bot] opened a new issue, #1992: URL: https://github.com/apache/iceberg-rust/issues/1992
> Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM | Details | | | ------------------- | ---------------------------------------------- | | Package | `rkyv` | | Version | `0.7.45` | | URL | [https://github.com/rkyv/rkyv/issues/644](https://github.com/rkyv/rkyv/issues/644) | | Date | 2026-01-05 | | Patched versions | `>=0.8.13` | The `SharedPointer::alloc` implementation for `sync::Arc<T>` and `rc::Rc<T>` in `rkyv/src/impls/alloc/rc/atomic.rs` (and `rc.rs`) does not check if the allocator returns a null pointer on OOM (Out of Memory). This null pointer can flow through to `SharedPointer::from_value`, which calls `Box::from_raw(ptr)` with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as `rkyv::from_bytes` or `rkyv::deserialize_using`) if an OOM condition occurs during the allocation of the shared pointer. The issue is reachable through safe code and violates Rust's safety guarantees. See [advisory page](https://rustsec.org/advisories/RUSTSEC-2026-0001.html) for additional details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
