An issue was discovered in the image crate before 0.23.12 for Rust. A Mutable reference has immutable provenance. (In the case of LLVM, the IR may be always correct.)

Affected: crates.io: image

A mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::as_ptr. Instead, slice::as_mut_ptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.

Affected: crates.io: image

A mutable reference to a struct was constructed by dereferencing a pointer obtained from `slice::as_ptr`. Instead, `slice::as_mut_ptr` should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.

There is no evidence for miscompilation, exploitable or otherwise, caused by this bug. [Further investigation on Zulip][Zulip] suggests that the unoptimized generated LLVM IR does not contain any UB itself, effectively mitigating further effects.

[Zulip]: https://rust-lang.zulipchat.com/#narrow/stream/146229-wg-secure-code/topic/Implications.20of.20using.20.60slice.3A.3Aas_ptr.60.20for.20mutable.20access/near/216499472

Affected: Ubuntu:24.04:LTS: rust-image, Ubuntu:25.10: rust-image, Ubuntu:26.04:LTS: rust-image

An issue was discovered in the image crate before 0.23.12 for Rust. A Mutable reference has immutable provenance. (In the case of LLVM, the IR may be always correct.)